zlacker

[return to "The state of binary compatibility on Linux and how to address it"]
1. sylwar+p1[view] [source] 2025-04-01 22:38:52
>>generi+(OP)
This article missed a critical point which is "the right way" to select a glibc ABI version: see binutils ld documentation, second part of the page related to VERSION support. This must include glibc internal symbols.

This will allow to craft ELF binaries on a modern distro which will run on "older" distros. This is critical for games and game engines. There is an significant upfront only-once work in order to select an "old" glibc ABI.

The quick and dirty alternative being having a toolchain configured to link with an "old" glibc on the side.

This article missed the -static-libstdc++ critical option for c++ applications (the c++ ABI is hell on earth), but did not miss the -static-libgcc and the dynamic loading of system interface shared libs.

◧◩
2. vlovic+88[view] [source] 2025-04-01 23:45:56
>>sylwar+p1
Which works if you use binutils ld. Does it work with mold or gold? And then how do you use this with languages other than c++/c like Go or Rust?
◧◩◪
3. rjsw+Oa[view] [source] 2025-04-02 00:19:29
>>vlovic+88
I thought that Go invoked syscalls directly instead of going through libc.
[go to top]