|Subject:||LD_LIBRARY_PATH in wrapper scripts|
|Date:||Sat, 21 Aug 2021 07:56:49 -0700|
|User-agent:||Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.13.0|
Hello there! We have an autotools-based build system setup with a custom GCC where we take all build- and run-time dependencies (except for glibc) from /opt. Things have worked well on Ubuntu 16, yet I'm hitting a funky issue when building on Ubuntu20 (libtool 2.4.6-14 according to dpkg). The issue comes down to one of the wrapper scripts that contains this gem:
# Add our own library path to
Most of our libs are statically linked with exception of just
one. So tests/apps that use that shared lib end up with libtool
wrappers... and they work correctly on Ubuntu16 (libtool 2.4.6-0.1
according to dpkg). It seems that libtool version just does not
stamp out this extra variable...
The manual fix is to remove the "/usr/lib/x86_64-linux-gnu" bit from the LD_LIBRARY_PATH above... and yet I have no idea where it came from or whether there is a way to influence its composition from a Makefile.am file.
I'd appreciate any and all suggestions.
Thanks in advance,
|[Prev in Thread]||Current Thread||[Next in Thread]|