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: <01bb01c09b4b$5281e1b0$0200a8c0@voyager>
From: "Trevor Forbes" <trevorforbes AT ozemail DOT com DOT au>
To: <cygwin-apps AT cygwin DOT com>
References: <20010219213847 DOT F23112 AT redhat DOT com>
Subject: Re: gcc questions prior to -8 release
Date: Wed, 21 Feb 2001 00:12:15 +0930
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


> From: Christopher Faylor <cgf AT redhat DOT com>
........
> 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.

I prefer to stick with -mno-win32 as the default, include
/usr/include/w32api by default and if possible, have an option to be able
remove the w32api inclusion should it be required.


Regards Trevor