On 2022-09-06 11:17:27 +0200, Vincent Lefevre wrote:
> On 2022-09-06 10:12:23 +0200, Frederic Berat wrote:
> > The behavior is likely not due to patches on libtool (at least I
> > couldn't find anything obviously relevant), but more probably to the
> > default behavior of gnu ld.
> > From the behav
On 2022-09-06 10:12:23 +0200, Frederic Berat wrote:
> The behavior is likely not due to patches on libtool (at least I
> couldn't find anything obviously relevant), but more probably to the
> default behavior of gnu ld.
> From the behavior described in the thread earlier, it looks like
> Debian has
Hello,
> As for why RHEL behaves differently, I remember that RHEL patches libtool so
> unless you installed from source you might take a look at whether you're
> running a modified install.
The behavior is likely not due to patches on libtool (at least I
couldn't find anything obviously releva
I've run into situations like this on RHEL 6 and 7 with libtool 2.4.6. My
approach was manually write a recipe to link a shlib looking in `.libs/'
and avoid the wrapper to be used at "build time".
The wrapper is made redundant by `RUNPATH' in my opinion when used with
`$ORIGIN'; but your mileage m
On Mon, Sep 05, 2022 at 04:35:43AM +0200, Vincent Lefevre wrote:
> 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
> >
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
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 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
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
