Subject: Re: bug#18916: libtool-2.4.3 caused autoconf test failure

From: "Gary V. Vaughan" <[email-masked]>
Date: Sun, 2 Nov 2014 18:51:43 +0000

On Oct 31, 2014, at 10:11 PM, Eric Blake <[email-masked]> wrote:
> 
> [adding libtool]
> 
> On 10/31/2014 10:54 AM, Bruce Dubbs wrote:
>> From the test output:
>> 
>> Compatibility with other tools.
>> 
>> 501: Libtool                                  FAILED (foreign.at:61)
>> ------
>> This was caused by libtool-2.4.3.  Using the identical instructions when
>> libtool-2.4.2 is used, the test passes.
> 
> Thanks for the report.  Yes, autoconf should be taught to be more
> tolerant of new libtool, but this is probably also worth investigating
> if it is a libtool regression worth fixing for the upcoming 2.4.4.

The failure is because latest libtool (and libtoolize et. al) are following
the rest of GNU in eschewing `backtick opening quotes' in favour of 'regular
single quotes at both ends' style.

The sed expression in foreign.at at line 60 should accept either format to
be compatible with new and old libtoolize output.  E.g.:

  AT_CHECK([sed -n ["s,^[^']*[\`']\\(/[^']*\\)'.*,\\1,p"] stdout], [0], [stdout])

Cheers,
-- 
Gary V. Vaughan (gary AT gnu DOT org)