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
X-Apparently-From: <earnie?boyd AT yahoo DOT com>
Message-ID: <3AE07A27.3AAC7BE5@yahoo.com>
Date: Fri, 20 Apr 2001 14:04:23 -0400
From: Earnie Boyd <earnie_boyd AT yahoo DOT com>
Reply-To: Cygwin Apps <cygwin-apps AT cygwin DOT com>
X-Mailer: Mozilla 4.76 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Cygwin Apps <cygwin-apps AT cygwin DOT com>
Subject: GCC -mno-cygwin vs mingw32-gcc cross environment.
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

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

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

Comments?

Earnie.

_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com