-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 According to Sam Steingold on 9/12/2009 10:16 PM: > > replacing "m4_toupper" with "upcase" resulted in a "good" configure with, > e.g., "upcase(ffi)" instead of "FFI". Where is upcase defined? It isn't provided by autoconf. > replacing it with "m4_upcase" resulted in > > configure:4249: error: possibly undefined macro: m4_upcase > If this token and others are legitimate, please use m4_pattern_allow. > See the Autoconf documentation. > That's because there isn't a macro m4_upcase; it is spelled m4_toupper. But I do see an issue with using m4_toupper - it does not quote its result, so if the result resembles a macro name, that macro will be expanded before anything else gets a chance to use the result of the upper-casing. I don't think we can change the semantics of this (there may be existing code relying on this), but we probably need to add safer counterparts that return a quoted string. - -- Don't work too hard, make some time for fun as well! Eric Blake ebb9@xxxxxxx -----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/ iEYEARECAAYFAkquMhQACgkQ84KuGfSFAYCwGwCfbcBIlsYJEgaMRcBwg6W3Q5AS QFcAnjIM4PZohogf/k2Q4XvFrpz8oRNS =bxgp -----END PGP SIGNATURE----- _______________________________________________ Autoconf mailing list Autoconf@xxxxxxx http://lists.gnu.org/mailman/listinfo/autoconf
