I have a library and tools that uses autotools for building. It
generates some modules that get loaded at runtime by searching
LD_LIBRARY_PATH and then a libexec directory.
On a current Ubuntu system (22.04.1, automake 1.16.5, autoconf 2.71,
libtool 2.4.6) and an older Ubuntu system (20.04.5, aut
On 2022-09-04 12:21:58 -0500, Corey Minyard wrote:
[...]
> I haven't figured out why, and I can't find a way to force libtool to
> put in the LD_LIBRARY_PATH. What am I doing wrong?
Look at the line "shlibpath_overrides_runpath=" in the generated
libtool script. I suspect that you have "yes" in o
On Mon, Sep 05, 2022 at 02:27:03AM +0200, Vincent Lefevre wrote:
> On 2022-09-04 12:21:58 -0500, Corey Minyard wrote:
> [...]
> > I haven't figured out why, and I can't find a way to force libtool to
> > put in the LD_LIBRARY_PATH. What am I doing wrong?
>
> Look at the line "shlibpath_overrides_
On 2022-09-04 20:52:07 -0500, Corey Minyard wrote:
> It compiles a program with -rpath and expects to see the set rpath
> appear after RUNPATH. On the system that works:
>
> $ gcc -o hello hello.c -Wl,-rpath -Wl,/foo
> $ objdump -p hello | grep RUNPATH
> RUNPATH /foo
>
> How
