Re: Shared library defines a RPATH
On Mon, Jul 29, 2002 at 07:28:12PM +0200, Michael Teichgräber wrote:
> this is what libtool seems to do if the generated shared library does
> not depend on another library that is not in a standard library path
> (as /lib). But, if a library foo is linked against another (libtool)
> libfoo2.la library, the -rpath is not stripped from the linker
I get the impression (although I might be mistaken) that you are trying
to install libraries into a non-standard path, which isn't searched for
in the "standard" /etc/ld.so.conf, so libtool feels it needs to add the
rpath so it can locate it.
If so, this is one situation I have not encountered (all my libraries
go into /usr/lib), so I can't comment further. I suggest filing a bug
report against libtool (wishlist or otherwise). In libtool source,
there is the variable "hardcode_into_libs". I would guess (but haven't
tested it) that changing this to "no" would fix the problems, but
haven't tested this.
If, however, I am completely confused, can you please answer the
Is this *.la file installed, or part of the source tree? If it
is part of the source tree, I will assume it is part of the same
If this *.la file is in the source tree, where is its final destination?
If this *.la file is installed, where was it installed?
 My reading of the source code suggests these are standard locations:
Brian May <firstname.lastname@example.org>
To UNSUBSCRIBE, email to email@example.com
with a subject of "unsubscribe". Trouble? Contact firstname.lastname@example.org