X-Spam-Check-By: sourceware.org Date: Thu, 12 Jan 2006 13:53:50 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: Define _POSIX_SOURCE in cygwin's features.h? Message-ID: <20060112185350.GG30108@trixie.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com References: <20060112181339 DOT GC30108 AT trixie DOT casa DOT cgf DOT cx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.11 Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On Thu, Jan 12, 2006 at 06:22:11PM -0000, Dave Korn wrote: >Christopher Faylor wrote: >> On Thu, Jan 12, 2006 at 07:08:32PM +0100, Samuel Thibault wrote: >>>But a portable program should _not_ assume that #defining _GNU_SOURCE >>>implies that _POSIX_SOURCE. If a program not only needs posix stuff >>>but also some GNU extras, it should #define _GNU_SOURCE _and_ >>>_POSIX_SOURCE itself. >> >>I don't care about portable programs. I'm interested in hearing if >>this will fix problems with programs which build without problem on >>linux. > >But it seems that it only builds "without problem" on Linux by chance, >not by design. That is by no means clear but even if that was the case, I don't care. >I don't see why we should try and fix this in cygwin. > >Consider how many times people come here and say "My app works fine on >Linux, how come it just dies with a SEGV on cygwin" and someone points >out the trivially obvious buffer overrun and we have to explain how it >only ever worked on Linux by luck because of differences in the >environment and the way the stack is set up. If I could easily make cygwin behave exactly the same way so that a buffer overrun that worked on linux went undetected on cygwin, too, I'd do that? If there was some linker option to ensure that, I'd use it. The point of cygwin isn't that it is a place where you find bugs which you should have fixed on linux. Every place where there is a barrier to porting a program from linux to cygwin is YA opportunity for someone to give up in disgust or (maybe worse) send a "I get compile error" message here. But, I understand your opinion on the matter. cgf -- 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/