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:	Fri, 20 Apr 2001 22:16:04 +0400
From:	egor duda <deo AT logos-m DOT ru>
X-Mailer:	The Bat! (v1.45) Personal
Reply-To:	egor duda <cygwin-apps AT cygwin DOT com>
Organization:	deo
X-Priority:	3 (Normal)
Message-ID:	<97526857290.20010420221604@logos-m.ru>
To:	cygwin-apps AT cygwin DOT com
Subject:	Re: GCC -mno-cygwin vs mingw32-gcc cross environment.
In-reply-To:	<3AE07A27.3AAC7BE5@yahoo.com>
References:	<3AE07A27 DOT 3AAC7BE5 AT yahoo DOT com>
Mime-Version:	1.0

Hi!

Friday, 20 April, 2001 Earnie Boyd earnie_boyd AT yahoo DOT com wrote:

EB> I've just successfully completed building a Cygwin native cross build
EB> environment for --target=mingw32.  While I'm cleaning up the code
EB> modifications I would like to ask if we should consider deprecating the
EB> -mno-cygwin switch in favor of the cross environment?

EB> I would rather see the cross build environment become standard because
EB> it is a natural for autoconfiguration.  You just add --host=mingw32 to
EB> the configuration scripts instead of needing to do CC='gcc -mno-cygwin'
EB> configure ... .

EB> Comments?

-mno-cygwin is currently used when building parts of cygwin itself. we
must be dealing with it somehow.

i don't think we should deprecate -mno-cygwin (i believe it's quite
handy sometimes) but rather discourage using it when it's natural to
configure with --host=mingw32

Egor.            mailto:deo AT logos-m DOT ru ICQ 5165414 FidoNet 2:5020/496.19

- Raw text -