[Top][All Lists]

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

Re: rpath for an inter-library dependency

From: Bert Wesarg
Subject: Re: rpath for an inter-library dependency
Date: Wed, 11 Feb 2015 21:39:41 +0100


On Wed, Feb 11, 2015 at 5:28 PM, Marcin Zalewski
<address@hidden> wrote:
> Hello.
> I have a contrib jemalloc library in my project that is not being
> built using libtool. When I build my libtool library, I add this to
> the link line:
> -ljemalloc -R/rpath/to/jemalloc
> This works fine, and my .la file includes:
> dependency_libs=' -R/rpath/to/jemalloc -ljemalloc'
> However, when I link my programs with the .la file, I do not get rpath
> on the liker line, which causes a run-time failure when the program is
> run. Am I using the -R option correctly? I was hoping that I could
> make it a dependency in my .la file and not have to worry about it.
> The documentation for -R says:
> If output-file is a program, add libdir to its run-time path. If
> output-file is a library, add -Rlibdir to its dependency_libs, so
> that, whenever the library is linked into a program, libdir will be
> added to its run-time path.
> As far as I understood this, once my library has this dependency, the
> rpath will be added to any program that links to my library, but that
> is not happening.

this is a known problem, though it seems that it is not considered as
one by the libtool team:


> Any help would be appreciated,
> -m

reply via email to

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