Hi Gary, Bob,
Thanks for your feedback!
In the end, I found Roumen Petrov replied to the list indicating that
setting lt_cv_sys_lib_dlsearch_path_spec when calling configure might
be able to solve this and indeed it did.
http://lists.gnu.org/archive/html/libtool/2014-08/msg4.html
By
On Tue, 2 Dec 2014, Filipe Brandenburger wrote:
I don't think that linking against libraries in DESTDIR is portable. DESTDIR
should be considered an install/copy-only option to support packaging.
Well, in my use case I'm often/usually cross compiling so having the
final libraries installed
[[former maintainers removed from Cc:]]
Hi Filipe,
On Aug 26, 2014, at 5:17 AM, Filipe Brandenburger filbran...@google.com
wrote:
Friendly ping?
+cc the libtool maintainers according to http://www.gnu.org/software/libtool/
If this is indeed a bug, I'd be willing to invest some time
On Fri, 28 Nov 2014, Gary V. Vaughan wrote:
Also, the use of -rpath is fairly deeply ingrained into the way that
automake generated rules call libtool, so if you want to tackle a complete
patch, there will be at least some work there too.
I suspect that there is a fairly good chance that the
Friendly ping?
+cc the libtool maintainers according to http://www.gnu.org/software/libtool/
If this is indeed a bug, I'd be willing to invest some time in trying
to fix it, but I'd need some pointers on what would be the proper way
to fix it...
I really think libtool should be creating a
Hi Filipe,
Filipe Brandenburger wrote:
Hi,
I'm trying to link binaries to libraries that are not installed on the
system, but just unpacked to a staging directory.
[SNIP]
Is this a libtool bug?
Any suggestions of workarounds?
(I also filed a bug at
Hi,
I'm trying to link binaries to libraries that are not installed on the
system, but just unpacked to a staging directory.
Consider this (real) example:
1) Build expat with --libdir=/usr/lib/${platform}
2) Install expat with make install DESTDIR=${stagedir}
3) Configure dbus with
