Andreas Enge <[email protected]> skribis: > When trying to use cdparanoia, I noticed the following: > > $ ldd `which cdparanoia` > > linux-vdso.so.1 => (0x00007fff1e9dd000) > libcdda_interface.so.0 => not found > libcdda_paranoia.so.0 => not found > libm.so.6 => > /nix/store/53afsq4c7r10hn77h3iyyavy2bs02403-glibc-2.17/lib/libm.so.6 > (0x00007fb37355b000) > librt.so.1 => > /nix/store/53afsq4c7r10hn77h3iyyavy2bs02403-glibc-2.17/lib/librt.so.1 > (0x00007fb373353000) > libc.so.6 => > /nix/store/53afsq4c7r10hn77h3iyyavy2bs02403-glibc-2.17/lib/libc.so.6 > (0x00007fb372fa5000) > libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 > (0x00007fb372d89000) > > /nix/store/53afsq4c7r10hn77h3iyyavy2bs02403-glibc-2.17/lib/ld-linux-x86-64.so.2 > => /lib64/ld-linux-x86-64.so.2 (0x00007fb373877000)
That’s an indication that cdparanoia doesn’t use Libtool... > The two missing libraries are part of the package itself; apparently, they > do not get encoded into the rpath. Could this be handled somehow by the build > system? Should it be done in the package definition? Or should I set an > LD_LIBRARY_PATH? In such cases, we must set the RUNPATH, using patchelf as Nikita notes. The recommended way to do that is to use ‘augment-rpath’ from (guix build rpath), as done in python.scm (make sure to add ‘patchelf’ as an input). HTH, Ludo’.
