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 X-Apparently-From: Message-ID: <3A9D07C1.C40A6F48@yahoo.com> Date: Wed, 28 Feb 2001 09:14:25 -0500 From: Earnie Boyd Reply-To: cygwin-apps AT cygwin DOT com X-Mailer: Mozilla 4.76 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: Jason Tishler CC: cygwin-apps AT cygwin DOT com Subject: Re: gcc questions prior to -8 release References: <20010219213847 DOT F23112 AT redhat DOT com> <20010228085315 DOT L449 AT dothill DOT com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Jason Tishler wrote: > > On Mon, Feb 19, 2001 at 09:38:47PM -0500, Christopher Faylor wrote: > > 2) If we want to stick with -mno-win32 as the default, should gcc > > include /usr/include/w32api by default? I really don't think that > > it should but I don't look forward to submitting changes to > > the stuff in sources.redhat.com that breaks as a result. > > Have we reached closure on the above? > > I can build the current Python CVS with gcc 2.95.2-6 but not 2.95.2-7 > unless I specify -I/usr/include/w32api. Will the "extra" option be > needed for 2.95.2-8 and later too? > > FWIW, I'm would like to get an appropriate patch into Python 2.1b1 > (scheduled for release tomorrow) to handle the above, if necessary. > You should be able to use `gcc -mwin32' instead of -I/usr/include/w32api. Since the /usr/include/w32api is for Win32 API's then `gcc -mwin32' makes more sense than -I/usr/include/w32api because it predefines the standard WIN32 macros. I believe that this is what Chris intends to do. Earnie. _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com