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
Date:	Sat, 17 Mar 2001 17:39:33 -0500
From:	Christopher Faylor <cgf AT redhat DOT com>
To:	cygwin-apps AT cygwin DOT com
Subject:	Re: gcc 2.95.3-1 and -mwin32
Message-ID:	<20010317173933.B1263@redhat.com>
Reply-To:	cygwin-apps AT cygwin DOT com
Mail-Followup-To:	cygwin-apps AT cygwin DOT com
References:	<20010317172830 DOT A24346 AT redhat DOT com> <00bf01c0af32$64478c10$0200a8c0 AT lifelesswks>
Mime-Version:	1.0
User-Agent:	Mutt/1.3.11i
In-Reply-To:	<00bf01c0af32$64478c10$0200a8c0@lifelesswks>; from robert.collins@itdomain.com.au on Sun, Mar 18, 2001 at 09:34:11AM +1100

On Sun, Mar 18, 2001 at 09:34:11AM +1100, Robert Collins wrote:
>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.

I forgot to mention that -mno-win32 will still "do the right thing".  It
will remove -I/usr/include/w32api entirely -- for the purists among us.

cgf

- Raw text -