New answers tagged dynamic-linking
In second strace part that tells about x32 binaries is strange, but unlikely: faccessat(AT_FDCWD, "/libx32/ld-linux-x32.so.2", X_OK) = -1 ENOENT (No such file or directory) Maybe cluster's /lib64/ld-linux-x86-64.so.2 dislikes your pin_sim.so somehow. To further troubleshoot the issue, try running /lib64/ld-linux-x86-64.so.2 --list ...
Cause It seems the '-pie' parameter breaks Sniper compilation. I tried adding it to my home machine and it fails with the exact same error. Removing it from the cluster line and the linker succeeds. As the user siblynx mentioned, OpenSUSE (at least the one in the cluster) enforces executables to use PIE when being linked, while Linux Mint doesn't. ...
My problem lay in the fact that I never ran ldconfig after installing everything. In order for shared object libraries to be found on Debian, you must run sudo ldconfig to rebuild the shared library cache.
Well, you can look at what gets exported using e.g. objdump, readelf or nm.
You can do a few things to help yourself understand this. ldd /usr/bin/cat On my laptop, that gives this output: 1771 % ldd /usr/bin/cat linux-vdso.so.1 (0x00007ffc37fba000) libc.so.6 => /usr/lib/libc.so.6 (0x00007f1ea7018000) /lib64/ld-linux-x86-64.so.2 (0x00007f1ea73bc000) You'll notice that linux-vdso.so.1 and libc.so.6 ...
Top 50 recent answers are included