fix(release): build Linux binaries as static musl to restore glibc 2.35 compatibility#479
Merged
platinummonkey merged 1 commit intomainfrom May 8, 2026
Merged
Conversation
platinummonkey
force-pushed
the
fix/linux-musl-static-build
branch
4 times, most recently
from
1f040c6 to
dc7ac8e
Compare
…35 compatibility Switches Linux release and CI builds from `*-unknown-linux-gnu` to `*-unknown-linux-musl` so the published binaries are fully statically linked and have no glibc dependency. Resolves the GLIBC_2.38/2.39 errors reported on Ubuntu 22.04 (jammy, glibc 2.35). - .goreleaser-linux.yaml: target the musl triples - .github/workflows/release.yml: install musl-tools + the messense aarch64-unknown-linux-musl cross toolchain, set per-target CC and linker env vars, build with `-C target-feature=+crt-static` - .github/workflows/ci.yml: mirror the release setup; build x86_64 and aarch64 musl sequentially and verify each binary with `file` (statically linked) and `ldd` (not a dynamic executable) - docs/ARCHITECTURE.md, docs/TROUBLESHOOTING.md: document the static linking and the glibc upgrade guidance for affected users Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
platinummonkey
force-pushed
the
fix/linux-musl-static-build
branch
from
dc7ac8e to
69ca572
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Fixes the GLIBC version compatibility issue reported where pup 0.58.3 fails to run on Ubuntu 22.04 (Jammy) with glibc 2.35. The binary was built against glibc ≥ 2.38, causing runtime errors on older systems.
Solution: Switch Linux release builds to fully static musl libc binaries that have no glibc dependency.
Changes
Release Pipeline (
.github/workflows/release.yml)*-gnuto*-musl(.goreleaser-linux.yaml:24-25)musl-toolspackage for x86_64-musl toolchainCI Pipeline (
.github/workflows/ci.yml)filecommand verifies "statically linked"lddverifies "not a dynamic executable"Documentation
docs/ARCHITECTURE.md: Added "Static Linking for Linux" section explaining musl approachdocs/TROUBLESHOOTING.md: Added "GLIBC version error on Linux" entry with upgrade instructionsTesting
cargo clippy --all-targets -- -D warningspassesVerification
After this change, Linux binaries will:
Release Notes
Users on Ubuntu 22.04 and other systems with glibc < 2.38 can now run pup after upgrading to the release containing this fix.
🤖 Implementation: pi + Kimi k2.5
📝 Planning: Claude Opus