-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 According to Paul Eggert on 9/4/2006 2:16 AM: > Eric Blake <ebb9@xxxxxxx> writes: > >> In the meantime, perhaps Autoconf should document that >> all autom4te input files should always end in newline. > > Naaaah. Let's just fix the bug in M4. It's clearly a bug. > The GNU tradition is to handle arbitrary input files, > and not to insist on "text" files in the POSIX sense. > Still, if I get M4 1.4.7 out before autoconf 2.61, it may be worth adding a test case to autoconf that tickles the 1.4.6 bug, so that users are less likely to install autoconf with a too-old M4 (although you may find, as I did for m4's testsuite, that portably getting a file without a newline in the testsuite is not easy :). I verified that only 1.4.6 has the bug; 1.4.5 works in this instance (but had other bugs). We already document that the testsuite fails at least one test with a too-old M4 version, although right now 1.4.5 passes the autoconf suite with flying colors. - -- Life is short - so eat dessert first! Eric Blake ebb9@xxxxxxx -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.1 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFE/CpD84KuGfSFAYARApMOAJ0UIICnvqsTR/SRfySsdTMyUF08jQCeKLqX dZf2cl/LcB1RdNvHektqxVY= =p8/b -----END PGP SIGNATURE----- _______________________________________________ Autoconf mailing list Autoconf@xxxxxxx http://lists.gnu.org/mailman/listinfo/autoconf
