-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 According to Matthew Woehlke on 3/1/2007 9:16 AM: >> That's because printf.c is part of gnulib, and both coreutils and m4 use >> the same source file. Whatever you do to fix it for one package will fix >> it for the other; and as Bruno suggested, if compiling with CFLAGS=-O >> fixes it (by detecting the brokenness of your compiler's long long), then >> it probably is not worth much further effort in gnulib to work around it. > > Well... aside from the fact that I forgot that (it's been quite a > while), I still think that if printf.c is going to *assume* unsigned if > long long exists, then config.h really ought to make this safe, say by > having something like this in config.h.in: > > #if defined(HAVE_LONG_LONG_INT) && !defined(HAVE_UNSIGNED_LONG_LONG_INT) > # undef HAVE_LONG_LONG_INT > #endif Is it worth patching autoconf's AC_TYPE_LONG_LONG_INT macro to declare that there is not a usable 'long long int' type if no corresponding unsigned long long type exists? - -- 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 iD8DBQFF8ztl84KuGfSFAYARAmn2AJ9yV8Hjvp2FGQHgM80mPZWpHS+IFACgrEFz Z81+npvIRgO9HL0rUj7XSfE= =XCfS -----END PGP SIGNATURE----- _______________________________________________ Autoconf mailing list Autoconf@xxxxxxx http://lists.gnu.org/mailman/listinfo/autoconf
