This is the mail archive of the
mailing list for the Cygwin project.
RE: Define _POSIX_SOURCE in cygwin's features.h?
- From: "Dave Korn" <dave dot korn at artimi dot com>
- To: <cygwin at cygwin dot com>
- Date: Thu, 12 Jan 2006 17:40:35 -0000
- Subject: RE: Define _POSIX_SOURCE in cygwin's features.h?
Christopher Faylor wrote:
> Someone on the cygwin irc channel had a problem building a package which
> would have been solved if Cygwin defined _POSIX_SOURCE.
> I know that Cygwin is not fully POSIX compliant (I really really do) but
> I'm wondering if setting _POSIX_SOURCE in the cygwin headers wouldn't
> solve more porting problems than it creates.
> Any opinions on this? Eric?
> P.S. I know that Cygwin isn't fully compliant with POSIX specifications.
As far as I can tell by googling, _POSIX_SOURCE, despite the leading
underscore, is in fact a user-land feature test macro that it is up to each
individual application to decide whether to switch it on or not according to
whether the application itself is compliant or not.
IOW, the system headers should have nothing to say about it at all, although
they may well want to react to it if it is defined at the time they are
Can't think of a witty .sigline today....
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html