This is the mail archive of the mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: gcc 2.95.3-1 and -mwin32

No objections either way. The autoconf macro will probably be useful
anyway if someone contributes the logic for WINE to it...

I've never had a problem with conflicts between w32api and the unix
files, and adding the appropriate logic to tell the difference between
native win32 and cygwin seems like a necessary step for a reliable port
any IMO.


----- Original Message -----
From: "Christopher Faylor" <>
To: <>
Sent: Sunday, March 18, 2001 9:28 AM
Subject: gcc 2.95.3-1 and -mwin32

> I've got gcc 2.95.3-1 ready to go.  It seems to work ok.
> I've had a private discussion with DJ about the affect of -mwin32.  We
> both feel that the windows header files should be included regardless
> whether this switch is included or not.  I think that Chuck Wilson
> persuasively argued this point.
> If we don't do this, then there are a lot of gratuitous changes
> for a lot of configurations.  I've had to change four or five
> on alone.
> So, while I appreciate all of the work that Robert Collins is doing to
> things working in autoconf, I've come to believe that the marginal
> of not including /usr/include/w32api outweigh the drawbacks.
> So, unless someone has a strong objection, the default for gcc
> gcc 3.0, and gcc 3.1 will be to include /usr/include/w32api.
> I'll wait a couple of days to see if anyone has any strong objections
> before I release the new version of gcc.
> cgf

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]