This is the mail archive of the
cygwin-apps@sources.redhat.com
mailing list for the Cygwin project.
Re: gcc questions prior to -8 release
- To: Jason Tishler <Jason dot Tishler at dothill dot com>
- Subject: Re: gcc questions prior to -8 release
- From: Earnie Boyd <earnie_boyd at yahoo dot com>
- Date: Wed, 28 Feb 2001 09:14:25 -0500
- CC: cygwin-apps at cygwin dot com
- References: <20010219213847.F23112@redhat.com> <20010228085315.L449@dothill.com>
- Reply-To: cygwin-apps at cygwin dot com
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