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: <mailto:cygwin-apps-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-apps/>
List-Post: <mailto:cygwin-apps AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-apps-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/lists.html#faqs>
Delivered-To: mailing list cygwin-apps AT sources DOT redhat DOT com
Message-ID: <00bf01c0af32$64478c10$0200a8c0@lifelesswks>
From: "Robert Collins" <robert DOT collins AT itdomain DOT com DOT au>
To: <cygwin-apps AT cygwin DOT com>
References: <20010317172830 DOT A24346 AT redhat DOT com>
Subject: Re: gcc 2.95.3-1 and -mwin32
Date: Sun, 18 Mar 2001 09:34:11 +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 5.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
X-OriginalArrivalTime: 17 Mar 2001 22:28:27.0446 (UTC) FILETIME=[96318560:01C0AF31]

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.

Rob


----- Original Message -----
From: "Christopher Faylor" <cgf AT redhat DOT com>
To: <cygwin-apps AT cygwin DOT com>
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
of
> whether this switch is included or not.  I think that Chuck Wilson
also
> persuasively argued this point.
>
> If we don't do this, then there are a lot of gratuitous changes
required
> for a lot of configurations.  I've had to change four or five
directories
> on sources.redhat.com alone.
>
> So, while I appreciate all of the work that Robert Collins is doing to
get
> things working in autoconf, I've come to believe that the marginal
benefits
> of not including /usr/include/w32api outweigh the drawbacks.
>
> So, unless someone has a strong objection, the default for gcc
2.95.3-1,
> 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
>