ci(release): build Linux binaries on ubuntu-22.04 for older-glibc support#74
Merged
Conversation
…port Linux release binaries were built on ubuntu-latest (now Ubuntu 24.04, glibc 2.39), so they required GLIBC_2.38 and failed to start on older LTS distros (Debian 12 = 2.36, Ubuntu 22.04 = 2.35) with: libc.so.6: version `GLIBC_2.38' not found (required by webclaw-mcp) glibc is forward- but not backward-compatible, so the build host's glibc sets the floor. Pin both Linux targets to ubuntu-22.04 (glibc 2.35); the aarch64 cross toolchain tracks the runner distro, so this lowers both. Note: 2.35 still won't cover Amazon Linux 2023 / RHEL 9 (2.34) — full coverage needs a musl static build. Tracked in #73. Refs #73 Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This was referenced Jun 27, 2026
pull Bot
pushed a commit
to edsonllneto/webclaw
that referenced
this pull request
Jun 27, 2026
The gnu Linux binaries are glibc-floored (2.35 after 0xMassi#74), so they still won't run on Amazon Linux 2023 / RHEL 9 (glibc 2.34), Alpine, or anything older. Add fully static musl builds that run on ANY Linux regardless of glibc. Adds x86_64-unknown-linux-musl and aarch64-unknown-linux-musl to the build matrix, built with cargo-zigbuild (zig as the C/C++ cross-compiler for BoringSSL). Build scripts (bindgen) run as the glibc host so libclang loads, and the linked output is fully static. A native Alpine build can't do this — its static build scripts can't dlopen libclang. musl assets ship ALONGSIDE the gnu ones (gnu stays default; musl is the runs-anywhere fallback). The release job globs *.tar.gz, so the new assets are checksummed + uploaded automatically; the docker/homebrew jobs enumerate gnu targets explicitly and are unaffected. Validated in Docker: cargo-zigbuild produced a fully static aarch64-musl webclaw-mcp (ldd: not a dynamic executable) that answered an MCP handshake on Alpine, Debian 11 (glibc 2.31), Debian 12, Amazon Linux 2023 (2.34), and Ubuntu 24.04 — everywhere, including where the gnu builds fail. Closes 0xMassi#73 Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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.
Partially addresses #73.
Problem
Linux release binaries were built on
ubuntu-latest(now Ubuntu 24.04, glibc 2.39), so they requiredGLIBC_2.38and failed to start on older LTS distros:glibc is forward- but not backward-compatible, so the build host's glibc sets the floor.
Change
Pin both Linux build-matrix targets to
ubuntu-22.04(glibc 2.35). The aarch64 target cross-compiles using the runner's apt toolchain, so its target glibc tracks the runner distro too — this lowers both x86_64 and aarch64.Only the two build-matrix
os:values change. The orchestration jobs (checksums, Homebrew) keepubuntu-latestsince their glibc is irrelevant.Coverage after this
ubuntu-20.04(glibc 2.31) would cover the 2.34 distros, but GitHub retired that runner in 2025, so 22.04 is the practical floor. Full coverage (Amazon Linux 2023, RHEL 9, anything older) needs a musl static build — that remains tracked in #73.Note
Takes effect on the next release tag — existing
v0.6.13assets are unchanged until a new release is cut.🤖 Generated with Claude Code