Skip to content

Conversation

@MiaM1ku
Copy link

@MiaM1ku MiaM1ku commented Dec 11, 2025

Problem

The current nightly release (pumpkin-X64-Linux) is linked against glibc 2.39, so it fails on older distributions with:

GLIBC_2.39 not found

Solution

Add a new job build_release_static that compiles for x86_64-unknown-linux-musl and uploads the fully-static binary.
The new artifact is named pumpkin-x86_64-linux-musl and is shipped together with the existing GNU build in the nightly release.

Changes

  • Install musl-tools (provides x86_64-linux-musl-gcc)
  • Add rustup target add x86_64-unknown-linux-musl
  • Build with cargo build --release --target x86_64-unknown-linux-musl
  • Include the static binary in draft_release

Verification

  • CI passes
  • Artifacts contain pumpkin-x86_64-linux-musl
  • Downloaded binary shows statically linked via file pumpkin-x86_64-linux-musl

Added a new job to build a static binary using musl and updated dependencies for the draft release step.
Add step to install musl-tools in CI workflow
Copy link

@illyrius666 illyrius666 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the comments, remove them or make them english.

MiaM1ku and others added 2 commits December 11, 2025 22:46
Co-authored-by: Illyrius <[email protected]>
Co-authored-by: Illyrius <[email protected]>
@MiaM1ku MiaM1ku marked this pull request as ready for review December 11, 2025 14:46
@MiaM1ku MiaM1ku requested a review from illyrius666 December 11, 2025 15:03
@HttpRafa
Copy link
Contributor

HttpRafa commented Jan 4, 2026

We could also use cargo-zigbuild to build Pumpkin for an older glibc version. This might avoid some of the negative effects of using musl, such as increased binary size.

@Snowiiii
Copy link
Member

Hey, I'm sorry but i don' think this is necessary and the "userbase" for this is very small, glibc 2.39 released a year ago, enough time for the most distros to update their glibc package, Also if using an older distro the user still always has the option to install glibc manually

@Snowiiii Snowiiii closed this Jan 14, 2026
@MiaM1ku
Copy link
Author

MiaM1ku commented Jan 14, 2026

Hey, I'm sorry but i don' think this is necessary and the "userbase" for this is very small, glibc 2.39 released a year ago, enough time for the most distros to update their glibc package, Also if using an older distro the user still always has the option to install glibc manually

For some users, there are various reasons why they may still be on older systems. Upgrading glibc is not as straightforward as it might seem and can easily introduce system instability or breakages. Keeping a statically linked build provides a safer alternative and helps these users avoid the risks associated with manually upgrading glibc.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants