-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 According to Bruno Haible on 5/27/2008 4:35 PM: | Eric Blake wrote: |> should m4/extensions.m4 blindly define |> _POSIX_SOURCE for Solaris, like it already does for Minix | | Certainly not. On many systems, _POSIX_SOURCE *prevents* system | extensions from being available. It's the opposite of _ALL_SOURCE (AIX), | _HPUX_SOURCE (HP-UX), _GNU_SOURCE (glibc).
Solaris documents that '_POSIX_SOURCE' followed by '__EXTENSIONS__' enables all extensions which don't conflict with POSIX. Yes, by itself, it is the opposite, but my proposal was adding it prior to __EXTENSIONS__. ~ Then again, since my tests showed that the mere definition didn't change behavior, and rather the addition of a link file (or the compiler name, as c89 is supposed to pull in values-xpg4.o under the hood), defining _POSIX_SOURCE on Solaris doesn't seem to help. - -- 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 iEYEARECAAYFAkg8m+QACgkQ84KuGfSFAYCCjQCdE8JpRnJBK0J031sls5c/esjB szkAoJITjdoW9ySwlQiDNfndEjjtkLw0 =Tmpt -----END PGP SIGNATURE-----
