diff options
| author | user <user@clank> | 2026-08-12 21:12:08 +0200 |
|---|---|---|
| committer | user <user@clank> | 2026-08-12 21:12:08 +0200 |
| commit | 03a2a8a8cbe30d8acf76420ba5143080cbf65d9e (patch) | |
| tree | fe89b79d6cdc3679dcfacc3499008d86d9d386f2 /docs | |
| parent | docs: record the target-dir symlink coupling and refresh stale provenance (diff) | |
| download | sl0ppi-03a2a8a8cbe30d8acf76420ba5143080cbf65d9e.tar.gz sl0ppi-03a2a8a8cbe30d8acf76420ba5143080cbf65d9e.tar.xz sl0ppi-03a2a8a8cbe30d8acf76420ba5143080cbf65d9e.zip | |
build: ship a static musl binary instead of a glibc-2.39 one
The gnu release build required GLIBC_2.39 (Jan 2024), so the "install it on
another machine" artifact would have failed on Debian 12, Ubuntu 22.04 and
RHEL 9. That is the whole premise of this repo, so it is a defect, not a nit.
make build -> cargo zigbuild --target x86_64-unknown-linux-musl
result -> ELF, statically linked, 0 GLIBC_ symbols, 51M
make build-gnu kept for fast local use
A musl build needs a musl C toolchain: isahc/curl pulls libz-sys and
libnghttp2-sys unconditionally (confirmed: --no-default-features does not drop
them). cargo-zigbuild + the ziglang python module were already installed here,
so this needs no sudo, no docker daemon and no system packages.
stage.sh now refuses to be quiet about it: it reports "statically linked" or
warns loudly that the artifact inherits the build box's libc.
Re-verified from the tarball in a throwaway HOME with node/npm/bun/cargo
replaced by poison stubs: static binary, pi 0.84.1 on the bundled bun, both wasm
plugins installed, session starts under a pty with no errors.
Remaining libc floor is bun's own glibc 2.17 (2012); bun publishes a musl build
if Alpine ever matters.
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/roadmap.md | 22 |
1 files changed, 17 insertions, 5 deletions
diff --git a/docs/roadmap.md b/docs/roadmap.md index 26f6680..c0425ff 100644 --- a/docs/roadmap.md +++ b/docs/roadmap.md @@ -43,11 +43,23 @@ Left for later (both need work disproportionate to their value right now): load. Only log line on a fresh profile is the benign "permission cache file not found". - [x] **found and fixed two real packaging bugs** (see below) -- [ ] decide `gnu` vs `musl` for the release target. Currently `gnu`, so the - binary inherits this box's glibc floor. The fork's toolchain already lists - `x86_64-unknown-linux-musl`; static musl is the better "runs on any box" - story and should probably become the default before anyone else installs - this. +- [x] **`musl` is now the release target.** The `gnu` build demanded + `GLIBC_2.39` (Jan 2024), so the tarball would have failed on Debian 12, + Ubuntu 22.04 and RHEL 9 -- the very machines this repo exists to install + on. The shipped binary is now `statically linked`, with zero `GLIBC_` + symbols. `stage.sh` fails loudly if a dynamically linked binary ever + sneaks back in. + + Cross-compiling needs a musl C toolchain, because `isahc`/curl drags in + `libz-sys` and `libnghttp2-sys` unconditionally (not behind + `vendored_curl`, so it cannot be feature-flagged away). We use + `cargo-zigbuild` + the `ziglang` python module, both already present on + this box: no sudo, no docker daemon, no system packages. + + The tarball's remaining libc floor is **bun's glibc 2.17** (2012), which + is effectively universal. If Alpine support is ever wanted, bun also + publishes `bun-linux-x64-musl.zip` -- a one-line change in + `fetch-vendor.sh`. - [ ] optional: `bun build --compile` pi into a single executable instead of shipping 183M of `node_modules` — but only if runtime-loaded `.ts` extensions still work in a compiled bundle. Test before committing to it. |
