Re: bootstrapping Autoconf with 2.63

[Eric Blake]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

According to Ralf Wildenhues on 3/14/2009 10:42 AM:
> | /usr/bin/m4:configure.ac:23: Warning: m4_eval: bad expression (bad input):  
> + _m4_bmatch_(
> 
> That's not good.  git Autoconf should be bootstrappable with the latest
> (and ideally also several prior!) released Autoconf.

Thanks for the report.  However, it worked just fine for me when I tried
it just now.  I'm wondering if it might be version-specific; I know at one
point, when the git version string resulted in 2.63-217-03118, that
m4_version_compare got confused by an invalid octal number.  This has
since been fixed in git, but may be the cause of your difficulties
bootstrapping.  Do you have some local commits that happen to have such an
octal number?  If that is the case, then the fix is as simple as
backporting the improved m4_version_compare into configure.ac, to override
the implementation in autoconf 2.63 that can't handle this case.

- --
Don't work too hard, make some time for fun as well!

Eric Blake             address@hidden
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkm+RTUACgkQ84KuGfSFAYDn/gCfWPdRgf98B+j2Tjqr/zfPIxcF
DJYAnA7MAhn6NgUe++5IPlANzTrveuXC
=fqfC
-----END PGP SIGNATURE-----