Mailing-List: contact cygwin-apps-help AT cygwin DOT com; run by ezmlm Sender: cygwin-apps-owner AT cygwin DOT com List-Subscribe: List-Archive: List-Post: List-Help: , Delivered-To: mailing list cygwin-apps AT cygwin DOT com Message-ID: <039401c182ba$e681f8d0$0200a8c0@lifelesswks> From: "Robert Collins" To: "Charles Wilson" , "CA List" Cc: "Danny Smith" References: <3C16B987 DOT EACB76F1 AT yahoo DOT com> <3C16C852 DOT 9070202 AT ece DOT gatech DOT edu> Subject: Re: gcc -mno-cygwin creates cygwin executables! Date: Wed, 12 Dec 2001 14:12:57 +1100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-OriginalArrivalTime: 12 Dec 2001 03:12:56.0934 (UTC) FILETIME=[E5857060:01C182BA] ----- Original Message ----- From: "Charles Wilson" > > Give me a week or two, well actually toward the middle of January. It's > > in the works. The question I have about this is, once we have a grand > > cross-compiler, should we get rid of -mno-cygwin? > > > IIRC, -mno-cygwin can't be removed because it is needed for the GNUpro > side of things. Also, we need it to build cygwin itself; do we really > want to require both a cygwin-gcc and a mingw-gcc in order to build > cygwin1.dll and setup.exe? setup.exe may well need that in the future, if the current issues with -mno-cygwin aren't ironed out (the old library that was floating round - may be fixed now, and the ongoing things like the cause of this email thread). Also the threading model for gcc for mingw is different than for cygwin, and that may cause trouble for setup unless -mno-cygwin is extended to change the threading model used in libgcc and in exception handling. Rob