patchelf
Fewer than 5 people recommend it so far, so there's no written verdict. Here is what commenters said.
3recommend
0warn against
Dec 21, 2025first mention
Jun 18, 2026latest mention
Why people recommend it
“Ah you can use https://github.com/NixOS/patchelf/pull/564”
Show 1 more
“OP would probably have a field day with NixOS's patchelf tool”
Caveats and dissent
No one in these comments warned against it.
Threads where it came up
- Migrating from GNU Stow to Chezmoi 1 mention
- Loss32: Let's Build a Win32/Linux 1 mention
- Win32 is the stable Linux ABI 1 mention
- ELF Crimes: Program Interpreter Fun 1 mention
Data: patchelf.json. Quotes are verbatim; the verdict and theme labels are written by a model from these comments, and every clause links to its sources.
All comments 4
“`patchelf` works.”
“Ah you can use https://github.com/NixOS/patchelf/pull/564”
Yes you can do this, thanks for mentioning I was interested and checked how you would go about it. 1. Delete the shared symbol versioning as per https://stackoverflow.com/a/73388939 (patchelf --clear-symbol-version exp mybinary) 2. Replace libc.so with a fake library that has the right version symbol with a version script e.g. version.map GLIBC_2.29 { global: *; }; With an empty fake_libc.c `gcc -shared -fPIC -Wl,--v
“OP would probably have a field day with NixOS's patchelf tool”