This is the mail archive of the
mailing list for the glibc project.
Re: autoconf AC_PREREQ ?
- From: "Carlos O'Donell" <carlos at systemhalted dot org>
- To: "Yann E. MORIN" <yann dot morin dot 1998 at anciens dot enib dot fr>
- Cc: libc-help at sourceware dot org
- Date: Tue, 30 Sep 2008 16:22:41 -0400
- Subject: Re: autoconf AC_PREREQ ?
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender :to:subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references :x-google-sender-auth; bh=amItfqpel6S34FyCnmEnXPx2bNx142ZQeZsdjzMdwJ0=; b=kIOrhqxBEUp73scYidqV8qWKIICjKR/xxwkj5678Xg1lC1io4Uy81BN5xO9ipqUXYg a3IRJQcub7Wau8S5joan3JFPae8YYAsVKcOhXwaAFyrr0LhjHatlr6OyYVCCmj++Dq3m fMOU6AoFcho/DdWAvGck35DYTHuCySKDEa/to=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references:x-google-sender-auth; b=JVMqFJuybcFc+PXxIDaeFxj2STlRaePuNYApB+COP7Xk+62S15Zrk3LiChdhwTWRvu EcdShB+Ym1e92tgnJJIdcO/lCLEJk2QhnlgKau6u/jgxadz96gduxw9xJxQfXF/zKH6U wsAQTfNWjPfRl4Fv52GUzeda0ft97R1G0NYKE=
- References: <firstname.lastname@example.org> <email@example.com> <firstname.lastname@example.org>
On Wed, Sep 24, 2008 at 1:37 PM, Yann E. MORIN
> Carlos, All,
> On Wednesday 24 September 2008 17:22:38 Carlos O'Donell wrote:
>> Why are you regenerating the configure scripts? Have you modified them?
> No I haven't. What's happening is that I svn heckout the eglibc tree, build
> a tarball with that for later re-use. Then, if I need to restart from fresh,
> I untar the tarball to avoid suffering a whole svn checkout.
> Then, make decide that the configure are out-of-date, and runs autoconf
> against the pre-requisite configure.in files. Hence mu problem.
You should touch all the configure scripts to avoid having them regenerate.
>> A CVS checkout will almost always have the wrong timestamp for the
>> configure.in files, therefore you should "touch" all the configure
>> scripts after checkout. This will avoid their regeneration.
>> The solution is to your problem is to set the environment variable
>> AUTOCONF to the correct autoconf binary e.g. export
> I by far prefer setting and exporting AUTOCONF rather than touching the
> files. It sounds saner, touching is going in the back of make.
That is also a good solution.
>> There is no need to guess, INSTALL says you must use autoconf2.53 or newer.
> So, why not state it explicitly in the configure.in files to avoid such
> problems? AC_PREREQ exists just for that! If the wrong autoconf version gets
> called, then a limpid error message is printed:
> FATAL ERROR: Autoconf version 2.50 or higher is required for this script
> instead of the more criptics:
> autoconf: Undefined macros:
> ***BUG in Autoconf--please report*** AC_FD_MSG
> ***BUG in Autoconf--please report*** AC_FD_CC
> which seem to imply that autoconf is at fault, when it's not.
> Thank you for the AUTOCONF= hint, I'll use that.
The glibc configure.in files are only fragments, and do not use
AC_INIT or AC_PREREQ.
The top-level configure file *does* specify the correct AC_PREREQ and
that is all that matters.