Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Date:	Tue, 18 Feb 2003 21:36:40 -0500
From:	Christopher Faylor <cgf AT redhat DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: [avail for test] libtool-devel-20030216-1
Message-ID:	<20030219023640.GE26147@redhat.com>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<3E519478 DOT 6050108 AT ece DOT gatech DOT edu> <007f01c2d797$5fb5d1e0$78d96f83 AT pomello> <3E52D4F7 DOT 5060803 AT ece DOT gatech DOT edu> <001301c2d7b5$cadc8fe0$78d96f83 AT pomello> <3E52EB44 DOT 40600 AT ece DOT gatech DOT edu>
Mime-Version:	1.0
In-Reply-To:	<3E52EB44.40600@ece.gatech.edu>
User-Agent:	Mutt/1.5.1i

On Tue, Feb 18, 2003 at 09:26:12PM -0500, Charles Wilson wrote:
>You can work around this with wrapper scripts (e.g. 'mgcc' contains 
>'exec gcc -mno-cygwin $*') but that's non standard.

However, it could easily be standard.  I could include a i686-pc-mingw32-gcc
and a i686-pc-mingw-ld in the gcc distribution.  And, I could also alias
all of the i686-pc-cygwin-* tools to i686-pc-mingw32-*.  That would provide
the equivalent of a cross compilation environment for cygwin.

Then you just have to say

configure --host=i686-pc-mingw32 --target=i686-pc-mingw32 --build=i686-pc-cygwin

and you bypass the arbitrary distinction of having a whole build system,
based on cygwin which exists just so that uname returns 'mingw', or whatever.

(Yes, I know that MSYS does other things, too, but this does get rid of
the requirement of using MSYS just to make it easy to use autoconf/libtool)

cgf

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -