-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 According to Aaron Ucko on 6/6/2009 7:26 PM: > Aaron Ucko <[email protected]> writes: > >> necessary for #include <limits.h> to yield a definition of PATH_MAX. > > Upon consideration, a better canary might be NAME_MAX or NGROUPS_MAX.
How is that? Are these more likely to be defined across all platforms than PATH_MAX, showing that limits.h was valid? Also, does changing which name we look for impact whether or not the -D_GCC_NEXT_LIMITS_H hack would be needed for your compiler? - -- Don't work too hard, make some time for fun as well! Eric Blake [email protected] -----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 iEYEARECAAYFAkovoiQACgkQ84KuGfSFAYDVcwCfQQK1rXNNMOChZctJIkUCvBfq L5AAnR4cHbnOBsK+PC55O5ABZ4uVE486 =acny -----END PGP SIGNATURE-----
