Package: libtool-bin Version: 2.4.6-2 Severity: normal I am developing a C library, which executes its unit tests as C files using
libtool --mode=execute ... This has to affect the value of LD_LIBRARY_PATH to ensure the executable for the test uses the newly-compiled library. Fair enough. Problem is, it doesn't respect an existing value for this variable and instead totally overwrites the old value, causing things that should be findable to not be. This matters, because I am in fact developing two C libraries, one that depends on the other. When I make install PREFIX=$HOME the lower library it lives in $HOME/lib and therefore I have to use LD_LIBRARY_PATH to make sure the second library can find it at runtime. Real programs can find it, but the unit tests for the second library cannot, because `libtool --mode=execute` has overwritten the value there. To fix this, it simply has to ensure that it prepends to, rather than overwrites, during its setup shell script. -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.13.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libtool-bin depends on: ii libtool 2.4.6-2 libtool-bin recommends no packages. libtool-bin suggests no packages. -- no debconf information -- Paul "LeoNerd" Evans [email protected] | https://metacpan.org/author/PEVANS http://www.leonerd.org.uk/ | https://www.tindie.com/stores/leonerd/
