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
Robert,
On Wed, Feb 11, 2015 at 9:46 PM, Robert Boehne wrote:
> So if I read these correctly, you specify the runtime path with -R but not
> the link time location with -L ?
where did you get the impression, that I did not specify -L in
conjunction with -R? We obviously do this, because linking
So if I read these correctly, you specify the runtime path with -R but not
the link time location with -L ? Does too run without help if you specify
both when you build your Libtool library?
Robert Boehne
On Feb 11, 2015 2:39 PM, "Bert Wesarg" wrote:
> Hi,
>
> On Wed, Feb 11, 2015 at 5:28 PM, M
Hi,
On Wed, Feb 11, 2015 at 5:28 PM, Marcin Zalewski
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 fil
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, whe
