If you happen to run into a package using older 2.13 autoconf, you have to use the "CFLAGS=foo ./configure". Otherwise you get this:
<snip>
Now before you scream that 2.13 is ancient, it still used in lots of places for whatever reason. The above example was from running the toplevel configure script on the sourceware.org 'src' tree (which is home to binutils, gcc, newlib, cygwin, gdb, and many others.) Toplevel is still stuck at 2.13 even though many subdirs have switched to modern autoconf.
Two options here: * The user is knowingly using an ancient version. Then, this user should have told you that. * The user does not know the version he/she is using is old. Then the user should just upgrade anyway.
The "configure VAR=value" is the modern way but it breaks on older versions, so "VAR=value configure" is easier to tell someone in an email and expect it to work.
But this use is discouraged. Andre Caldas. _______________________________________________ Autoconf mailing list Autoconf@xxxxxxx http://lists.gnu.org/mailman/listinfo/autoconf
