Subject: Re: libtool problem with runtime shlib path propagation
To: Todd Vierling <firstname.lastname@example.org>
From: Nick Hudson <email@example.com>
Date: 02/15/2002 08:22:05
On Friday 15 February 2002 8:16 am, Nick Hudson wrote:
> On Thursday 14 February 2002 6:52 pm, Todd Vierling wrote:
> > On Wed, 13 Feb 2002, Matthias Drochner wrote:
> > : A package builds a shared library (using libtool) which
> > : depends on X11 libraries.
> > : The linker call looks like
> > : libtool --mode=link cc -o lib.la *.lo -L/usr/X11R6/lib
> > : -lX11
> > When using libtool, the correct option is "-rpath". -Wl,-R should only be
> > used by non-libtoolized packages. libtool converts "-rpath" to the linker
> > options detected by libtool's configure step.
> I don't think this is the required option here.
> -rpath is used by libtool to denote the install location of a library. If a
> library is linked (using libtool) against the resulting libfoo.la file then
> this "install" directory will appear in the DT_RPATH of this new library.
This bit is right.
> The option to libtool's -rpath will not appear in the DT_RPATH of the
> resulting library.
...but this bit is apparently wrong. The option to -rpath does appear in the
DT_RPATH. That seem's wrong to me... just because libfoo.la gets installed
into a directory doesn't mean any of it dependencies are there.