[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Libtool problem with shared lib in non-standard directory

From: Ralf Wildenhues
Subject: Re: Libtool problem with shared lib in non-standard directory
Date: Mon, 9 Jan 2006 00:00:32 +0100
User-agent: Mutt/1.5.9i

Hi Marcel,

* Marcel Loose wrote on Thu, Jan 05, 2006 at 12:31:35PM CET:
> I encountered a problem where libtool does not add a -rpath to all the
> libs it adds on the link line. I'll try to describe the problem.
> I have two packages that are developed in-house, let's call them A and
> B. Package B depends on the (static) library of package A. Package A
> depends on a shared third party library that is installed in a
> non-standard directory (e.g. /non/standard/lib).
> Now the following problem arises. When I build an executable from
> package B, libtool adds the libraries that package A depends upon in
> the link command. One of these libs is, of course, the third party lib
> that is installed in /non/standard/lib. The link command does contain
> a -L/non/standard/lib specification, but it does not contain a
> -Wl,-rpath,/non/standard/lib specification. As a result, any
> executable from package B cannot be run unless the user explicitily
> adds /non/standard/lib to its LD_LIBRARY_PATH, which is IMHO
> undesirable.

Thanks for this bug report.  It would fit better on the bug-libtool
mailing list, so I'm Cc:ing there.  Please remove the automake list
from followups.

Please state your operating system this happens on, the exact libtool
version used, and show both the link line (libtool --mode=link ...)
and what libtool outputs.  Also, the compiler used, and possibly
`./libtool --config' would be useful.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]