X-Spam-Check-By:	sourceware.org
Date:	Thu, 12 Jan 2006 12:31:04 -0500
From:	Christopher Faylor <cgf-no-personal-reply-please AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Define _POSIX_SOURCE in cygwin's features.h?
Message-ID:	<20060112173104.GA30011@trixie.casa.cgf.cx>
Reply-To:	cygwin AT cygwin DOT com
Mime-Version:	1.0
User-Agent:	Mutt/1.5.11
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com

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?

cgf

P.S.  I know that Cygwin isn't fully compliant with POSIX specifications.

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -