-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 According to Paul Eggert on 12/8/2006 5:31 PM: > Eric Blake <ebb9@xxxxxxx> writes: > >> 2.13 to 2.59), but is it worth excluding AS_FOR_TARGET from the Autoscan >> reserved namespace since it is in heavy use in real-world configure scripts? > > I assume AS_FOR_TARGET is some macro provided by the GCC developers? Actually, it is a shell variable, similar to CC or AS, but designed to allow cross-compilation. > If so, I'm afraid I'd rather just let them live with m4_pattern_allow, > as it's a useful reminder of the need to worry about AS_* macros. It's unfortunate that the name of the cross-assembler environment variable and the macro prefix chosen by autoscan interfere in this manner. I don't really have a strong opinion on whether the m4_pattern_allow should belong to gcc or to autoconf, but either way, it is needed in order for gcc compilation to work. - -- Life is short - so eat dessert first! 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 iD8DBQFFehar84KuGfSFAYARAuh4AKCZObo4ppj4FQkPeiUySV72aKuY1gCcC3ts SMCm6BtPFAMTgssNwGYLmY0= =+Tyj -----END PGP SIGNATURE----- _______________________________________________ Autoconf mailing list Autoconf@xxxxxxx http://lists.gnu.org/mailman/listinfo/autoconf
