-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 According to Bob Proulx on 1/15/2007 5:06 PM: > > So this is the complete list as I know it. Update these and make sure > you have m4-1.4.8 available before building autoconf or the resulting > autoconf will not work right. (Unfortunately it will still pass all > of the tests though.) Actually, autoconf will work with the 10-year-old m4 1.4, which is why we made an effort to ensure the autoconf 2.61 testsuite works for the entire m4 1.4.x range. But by using an older m4, you are exposing yourself to the potential that a poorly written .m4 file used by your project (or even a malicious .m4 file that someone manages to get in autom4te's path) can cause a core dump, or on some architectures, the execution of random code. The recommendation for using 1.4.8 is not a hard requirement, merely a good idea. However, it IS a hard requirement that you use GNU M4 1.4 or later; other vendor's m4 implementations, as well as GNU M4 1.3 or earlier, are insufficient. - -- Don't work too hard, make some time for fun as well! Eric Blake ebb9@xxxxxxx -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFrD3d84KuGfSFAYARAgrQAJ4+e5/TiYW0Ibjo0Jt0NkRKQY4TcQCfeGMw 9u+2WeD+BOdIX5ux9VSy/xk= =+UXH -----END PGP SIGNATURE----- _______________________________________________ Autoconf mailing list Autoconf@xxxxxxx http://lists.gnu.org/mailman/listinfo/autoconf
