Mailing-List: contact cygwin-apps-help AT sourceware DOT cygnus DOT com; run by ezmlm Sender: cygwin-apps-owner AT sourceware DOT cygnus DOT com List-Subscribe: List-Archive: List-Post: List-Help: , Delivered-To: mailing list cygwin-apps AT sources DOT redhat DOT com Message-ID: <3AB3F2F1.5ABD6A12@ece.gatech.edu> Date: Sat, 17 Mar 2001 18:27:45 -0500 From: "Charles S. Wilson" X-Mailer: Mozilla 4.75 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: Robert Collins CC: cygwin-apps AT cygwin DOT com Subject: Re: gcc 2.95.3-1 and -mwin32 References: <20010317172830 DOT A24346 AT redhat DOT com> <3AB3ECE7 DOT 26B3D8D3 AT ece DOT gatech DOT edu> <20010317180703 DOT A23000 AT redhat DOT com> <00e501c0af37$39461450$0200a8c0 AT lifelesswks> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit > > Charles Wilson wrote: > > >Q: Does that also mean that the default for gcc-2.95.3-1 > > >on cygwin will be to #define WIN32 & WINDOWS in addition > > >to merely including /usr/include/w32api in the include > > >path? e.g. that -mwin32 is the default now (again)? > Chris Faylor said: > > I wasn't planning on doing this, no. I still think that > > Cygwin should not define these unless asked. > > > > This does cause problems for some of the stuff in > > sources.redhat.com but they are minor compared to > > the effort of adding -mwin32 everywhere that > > it was needed. > > > > So, this is still different from gcc-2.95.2-1. Robert Collins asked: > Will -mwin32 still be present? I think it should if you > do not define WIN32. This complicates things somewhat; there would be *three* separate behaviors: default: include /usr/include/mingw, but don't #define WIN32 and friends. -mwin32 (& -mno-cygwin): include /usr/include/mingw, and #define WIN32 and friends. -mno-win32: don't include /usr/include/mingw, and don't #define WIN32. BUT, these three behaviors make sense to me, given the experiences we've had with gcc-2.95.2-7 ... -9. --Chuck