autoconf-patches
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH] tests: use configure.ac, not configure.in, with aclocal/auto


From: Eric Blake
Subject: Re: [PATCH] tests: use configure.ac, not configure.in, with aclocal/automake involved
Date: Sat, 21 Jul 2012 11:43:25 -0600
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:13.0) Gecko/20120615 Thunderbird/13.0.1

On 07/21/2012 09:43 AM, Stefano Lattarini wrote:
> Do so because future automake and aclocal versions (starting from 1.13)
> won't support 'configure.in' anymore as the name of the Autoconf input
> file.  Without this patch, the Autoconf testsuite experience some
> spurious failures when run with the development version of aclocal and
> automake installed somewhere in $PATH.
> 
> * tests/torture.at: Rename 'configure.in' to 'configure.ac' throughout.
> 
> Signed-off-by: Stefano Lattarini <address@hidden>
> ---
>  tests/torture.at | 28 ++++++++++++++--------------
>  1 file changed, 14 insertions(+), 14 deletions(-)

Are we ready to completely ditch configure.in?  Automake 1.4 requires
it, but even old stable distros like RHEL 5 use automake 1.9; and we
have documented the name change for years now.

At any rate, once we ditch configure.in in the testsuite, then we might
as well ditch it everywhere.  Or are you only ditching it for
interactions with automake, while it can still limp along for people
using old toolsets?  In that case, this patch (with Jim's fixes) is
probably okay.

I'm thinking autoconf 2.70 should warn loudly if configure.in is still
used, and then we can completely drop it for 2.71.

-- 
Eric Blake   address@hidden    +1-919-301-3266
Libvirt virtualization library http://libvirt.org



Attachment: signature.asc
Description: OpenPGP digital signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]