Guys,
Any chance that someone will finally commit the fixes to prevent the
POSIX_C_SOURCE warnings from showing up? I saw a number of posts on this
topic, but it still seems like it's not "officially committed"
In file included from /usr/include/string.h:50,
                 from /usr/X11R6/include/qcstring.h:46,
                 from /usr/X11R6/include/qstring.h:42,
                 from /usr/X11R6/include/qwindowdefs.h:44,
                 from /usr/X11R6/include/qobject.h:43,
                 from /usr/local/include/kconfigbase.h:28,
                 from /usr/local/include/kconfig.h:29,
                 from ksaveioconfig.cpp:20:
/usr/include/sys/cdefs.h:273: warning: `_POSIX_C_SOURCE' is not defined
/usr/include/sys/cdefs.h:279: warning: `_POSIX_C_SOURCE' is not defined
In article <20030830161813.GA28890@twisted.net> you write:>Any chance that someone will finally commit the fixes to prevent the >POSIX_C_SOURCE warnings from showing up? I saw a number of posts on this >topic, but it still seems like it's not "officially committed">/usr/include/sys/cdefs.h:273: warning: `_POSIX_C_SOURCE' is not defined >/usr/include/sys/cdefs.h:279: warning: `_POSIX_C_SOURCE' is not definedThe warnings are wrong,[1] so you should probably ask the GCC people about that. -GAWollman [1] That is to say, any identifier used in a preprocessor expression (after macro expansion) is defined to have a value of zero, and GCC should not be complaining about this.