Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT sourceware DOT cygnus DOT com>
List-Subscribe:	<mailto:cygwin-subscribe AT sourceware DOT cygnus DOT com>
List-Archive:	<http://sourceware.cygnus.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sourceware DOT cygnus DOT com>
List-Help:	<mailto:cygwin-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender:	cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To:	mailing list cygwin AT sourceware DOT cygnus DOT com
Date:	Wed, 29 Sep 1999 12:52:22 -0500 (CDT)
From:	"M. R. Brown" <marcusb AT csd DOT uwm DOT edu>
To:	cygwin AT sourceware DOT cygnus DOT com
Subject:	Using mingw32 to build cross-tools
Message-ID:	<Pine.OSF.3.96.990929124138.1615C-100000@alpha3.csd.uwm.edu>
MIME-Version:	1.0

A little off-topic, but...

Are there any issues involved with using mingw32 to build cross toolchains
of binutils, gcc-2.95, etc.?  I have sucessfully built a i686-pc-cygwin X
mips-sony-psx chain that built without issues (for details on the
"mips-sony-psx" target e-mail me personally), but I'm not sure if it would
work with mingw32 because most of the commands used by the configure and
build scripts run under, well, cygwin.  I've tried mixing mingw32 and
cygwin beta 19 in the past and all hell broke loose.  If anyone has tried
this, let me know.

Marcus

P.S. Now that I think about it, would a Canadian cygwin->mingw32->mips be
possible? Would that be the best way to go?


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com

- Raw text -