On Mon, Jan 12, 2009 at 10:53 AM, Julien Cristau <jcris...@debian.org> wrote: > On Mon, Jan 12, 2009 at 10:47:53 -0800, Ian Romanick wrote: > >> Does defining _GNU_SOURCE actually cause those other things to be >> defined? What happens if there are places in the Mesa code that check >> for, say, _POSIX_SOURCE to select a code path? I don't think anything >> like that exists today, but I'd rather be safe than sorry. > > Apparently so, looking at <features.h>: > > /* If _GNU_SOURCE was defined by the user, turn on all the other features. */ > #ifdef _GNU_SOURCE > # undef _ISOC99_SOURCE > # define _ISOC99_SOURCE 1 > # undef _POSIX_SOURCE > # define _POSIX_SOURCE 1 > # undef _POSIX_C_SOURCE > # define _POSIX_C_SOURCE 200112L > # undef _XOPEN_SOURCE > # define _XOPEN_SOURCE 600 > # undef _XOPEN_SOURCE_EXTENDED > # define _XOPEN_SOURCE_EXTENDED 1 > # undef _LARGEFILE64_SOURCE > # define _LARGEFILE64_SOURCE 1 > # undef _BSD_SOURCE > # define _BSD_SOURCE 1 > # undef _SVID_SOURCE > # define _SVID_SOURCE 1 > # undef _ATFILE_SOURCE > # define _ATFILE_SOURCE 1 > #endif
Do you want to push your patch, and I'll add another to reduce the macros to just _GNU_SOURCE? -- Dan ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ Mesa3d-dev mailing list Mesa3d-dev@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mesa3d-dev
