On Dec 1, 2014, at 5:39 AM, Gary V. Vaughan wrote:
> Yes, as you discovered, starting with Libtool-2.4.3 GNU M4 is required by
> libtoolize, because we now dynamically run the configure.ac through it to
> reliably detect build characteristics (as opposed to earlier releases which
> grepped and
Hi Lawrence,
> On 2 Dec 2014, at 08:05, Lawrence Velázquez wrote:
>
>> On Dec 1, 2014, at 5:39 AM, Gary V. Vaughan wrote:
>>
>> Yes, as you discovered, starting with Libtool-2.4.3 GNU M4 is required by
>> libtoolize, because we now dynamically run the configure.ac through it to
>> reliably d
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 passing
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 un
