Re: AC_PREREQ comes first in autoscan

2009-09-04 Thread Eric Blake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Ralf Wildenhues on 9/1/2009 11:38 AM: Hello, * NightStrike wrote on Tue, Sep 01, 2009 at 06:19:07PM CEST: This macro is the only macro that may be used before AC_INIT, This isn't even true. AC_DEFUN and m4_define, as well as

Re: AC_PREREQ comes first in autoscan

2009-09-04 Thread NightStrike
On Fri, Sep 4, 2009 at 8:22 AM, Eric Blakee...@byu.net wrote: Yes, indeed.  Pushing this (NightStrike, let me know if you'd rather have a real name instead of a pseudonym in THANKS): I prefer anonymity :) ___ Autoconf mailing list Autoconf@gnu.org

Re: AC_PREREQ comes first in autoscan

2009-09-04 Thread Ralf Wildenhues
Hi Eric, * Eric Blake wrote on Fri, Sep 04, 2009 at 02:22:54PM CEST: + Improve wording about what goes before AC_INIT. + * doc/autoconf.texi (Initializing configure): Update wording. + (Versioning) AC_PREREQ: Remove misleading text, to match + autoupdate's behavior. Thanks,

AC_PREREQ comes first in autoscan

2009-09-01 Thread NightStrike
Using autoconf 2.63 and autoscan, my automatically generated configure.scan has AC_PREREQ as the first macro in the file, and AC_INIT second. The autoconf manual has this to say about it: This macro is the only macro that may be used before AC_INIT, but for consistency, you are invited not to do

Re: AC_PREREQ comes first in autoscan

2009-09-01 Thread Ralf Wildenhues
Hello, * NightStrike wrote on Tue, Sep 01, 2009 at 06:19:07PM CEST: This macro is the only macro that may be used before AC_INIT, This isn't even true. AC_DEFUN and m4_define, as well as other m4sugar elements, are widely used before AC_INIT (when you consider that autoconf parses aclocal.m4