Re: [EXTERNAL] Re: LD_LIBRARY_PATH in wrapper scripts

2021-08-22 Thread Oleg Smolsky
On Sun, Aug 22, 2021 at 7:01 AM Bob Friesenhahn < bfrie...@simple.dallas.tx.us> wrote: > On Sat, 21 Aug 2021, Oleg Smolsky wrote: > >> > >> So, if libtool does not believe that /usr/lib/x86_64-linux-gnu is in > >> the default search path, it adds it. > >> > > Right, and my compiler is in

Re: [EXTERNAL] Re: LD_LIBRARY_PATH in wrapper scripts

2021-08-22 Thread Bob Friesenhahn
On Sat, 21 Aug 2021, Oleg Smolsky wrote: So, if libtool does not believe that /usr/lib/x86_64-linux-gnu is in the default search path, it adds it. Right, and my compiler is in /opt/gcc-11/ and so that addition to LD_LIBRARY_PATH is wrong. The system's compiler is older than what we use and

Re: [EXTERNAL] Re: LD_LIBRARY_PATH in wrapper scripts

2021-08-21 Thread Werner LEMBERG
>>> 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. [...] > > So far the cleanest hack I've found is to patch the generated > "libtool" script so that the generated test wrappers

Re: [EXTERNAL] Re: LD_LIBRARY_PATH in wrapper scripts

2021-08-21 Thread Oleg Smolsky
On Sat, Aug 21, 2021 at 4:25 PM Bob Friesenhahn < bfrie...@simple.dallas.tx.us> wrote: > On Sat, 21 Aug 2021, Oleg Smolsky wrote: > > > > > 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