Re: rpath for an inter-library dependency

[Marcin Zalewski]

Thanks Bert.

This is indeed exactly the same issue I am facing. I would like the
-rpath option to be added to all programs that use my .la library with
the -R flag in dependency_libs, but that is not happening. As far as I
understand, we agree that the documentation says that an -R flag in
.la lib should result in the appropriate -rpath flags to the linker
when a program linking to that library is compiled. So the patch in
your email thread does the trick? The solution seems very simple.

Regards,
Marcin

On Wed, Feb 11, 2015 at 3:39 PM, Bert Wesarg <address@hidden> wrote:
> Hi,
>
> 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:
>
> http://lists.gnu.org/archive/html/libtool/2011-11/msg00010.html
>
> Bert
>
>>
>> Any help would be appreciated,
>> -m