2 Jun
2023
2 Jun
'23
18:09
in trying to use a different version of gcc/+libs/+binutils I have run into a problem -- namely that ld seems to use a hard coded path (or two): /home/devel/root/usr/bin> ldd ./ld ./ld: /lib64/libc.so.6: version `GLIBC_2.34' not found (required by ./ld) linux-vdso.so.1 (0x00007ffcc6340000) libbfd-2.40.0.20230412-4.so => not found libctf.so.0 => not found libc.so.6 => /lib64/libc.so.6 (0x00007f724619b000) /lib64/ld-linux-x86-64.so.2 (0x00007f7246c7a000) The 'ld' prog from binutils ignores LD_LIBRARY_PATH and points to the root to resolve libc, a few other libs that are not found and ld-linux-x86-64.so.2 (hard-coded to /lib64 instead of using LD_LIBRARY_PATH Is this necessary?