-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 According to Bruno Haible on 5/23/2005 3:17 AM: >>Shouldn't that typedef of int64_t be protected by "#ifdef >>NEED_SIGNED_INT_TYPES"? > > NEED_SIGNED_INT_TYPES is only needed for Cygwin (so far). Let's correct this > when we stumble acess a system that has the same problem and uses the MSVC > compiler.
Which cygwin bug is this? Let's get it fixed in cygwin, rather than having to work around it. Looking at /usr/include/stdint.h on cygwin, I found one bug in cygwin 1.5.16 (and am proposing a patch there to get it fixed in 1.5.17): INTMAX_C(x) is defined as appending just L, but intmax_t is typedef'd to long long and INTMAX_MIN and friends are definitely 64-bit, so it should be appending LL. But there are definitions for int64_t, uint64_t, int_least64_t, uint_least64_t, int_fast64_t, and uint_fast64_t; all six with the appropriate MIN and MAX macros. And if the bug was in an earlier version of cygwin, I think gnulib can safely ignore that; there are a number of bugs in older cygwin versions that are simply not worth working around. - -- Life is short - so eat dessert first! Eric Blake [EMAIL PROTECTED] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCkcVu84KuGfSFAYARAm4gAJ0UFlXPY5winntDG/J4hnVwySGgwwCfQII0 vLSwVZVCfhi4PucgOZmQKQQ= =OI2e -----END PGP SIGNATURE----- _______________________________________________ bug-gnulib mailing list [email protected] http://lists.gnu.org/mailman/listinfo/bug-gnulib
