Martin Vogel 0fc2d9923b docs: the standard Linux binary needs glibc 2.35+, not 2.38+ ...

Built in the pinned ubuntu:22.04 container, the standard Linux binary
requires at most glibc 2.35 and GLIBCXX_3.4.30. Update the comments
that said 2.38+: install.sh, the npm and PyPI wrappers, cli.c, the
Homebrew formula, smoke-test.sh, _smoke.yml, check-glibc-compat.sh and
the local glibc-floor venue. The installers keep choosing the -portable
archive, since a 2.35 floor still excludes Debian 11, RHEL 8 and Ubuntu
20.04.

The local smoke-glibc-floor lane keeps its assertion and now says what
it proves: a binary built in the noble test image refusing to start
there shows the venue is older than the build image.

Refs #2486

Signed-off-by: Martin Vogel <martin.vogel.tech@gmail.com>

2026-11-02 04:02:21 +01:00

..

aur

revert(release): re-embed runtime assets into the single shipped binary

2026-08-09 13:06:42 +02:00

chocolatey

chore(pkg): sync packaging metadata to v0.12.1

2026-10-17 14:38:59 +02:00

glama

revert(release): re-embed runtime assets into the single shipped binary

2026-08-09 13:06:42 +02:00

go

chore(pkg): sync packaging metadata to v0.12.1

2026-10-17 14:38:59 +02:00

homebrew/Formula

docs: the standard Linux binary needs glibc 2.35+, not 2.38+

2026-11-02 04:02:21 +01:00

npm

docs: the standard Linux binary needs glibc 2.35+, not 2.38+

2026-11-02 04:02:21 +01:00

pypi

docs: the standard Linux binary needs glibc 2.35+, not 2.38+

2026-11-02 04:02:21 +01:00

scoop

chore(pkg): sync packaging metadata to v0.12.1

2026-10-17 14:38:59 +02:00

winget/manifests/d/DeusData/CodebaseMemoryMcp/0.8.1

fix(release): externalize runtime assets and harden VT verification

2026-08-08 17:35:05 +02:00