mirror of
https://github.com/ziglang/zig.git
synced 2025-12-10 00:03:10 +00:00
5d1aab72d9
When the Zig compiler is statically linked, it inspects the /usr/bin/env ELF file to determine the native glibc version, by checking the DT_RUNPATH, and then calling readlink() on the libc.so file, because typically the symlink will have e.g. libc-2.33.so in the name, revealing the glibc version. Fortunately, this information is also in readlink() of ld.so, which is available as the "INTERP" file path. This commit looks for e.g. `ld-2.33.so` on the symlink data for the dynamic linker. In theory a more complete solution would also look at `/etc/ld.so.cache` if necessary, and finally fall back to some hard coded paths, in order to resolve the location of libc.so, in order to do this readlink() trick on the resulting path. You can find that flow chart with `man ld.so`. But I think this logic will be enough to get a correct answer in all real world cases. This has been tested on Debian Buster and glibc-based Void Linux. Fixes #6469