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
Delivered-To:	mailing list cygwin AT cygwin DOT com
Message-ID:	<17B78BDF120BD411B70100500422FC6309E41A@IIS000>
From:	Bernard Dautrevaux <Dautrevaux AT microprocess DOT com>
To:	"'CU List'" <Cygwin AT cygwin DOT com>
Subject:	RE: Compiling apps to Mingw32 with cygwin
Date:	Thu, 10 Jan 2002 10:30:40 +0100
MIME-Version:	1.0
X-Mailer:	Internet Mail Service (5.5.2653.19)

> -----Original Message-----
> From: Earnie Boyd [mailto:earnie_boyd AT yahoo DOT com]
> Sent: Wednesday, January 09, 2002 8:42 PM
> To: CU List
> Subject: Re: Compiling apps to Mingw32 with cygwin
> 
> 
> > Subject: Re: Compiling apps to Mingw32 with cygwin
> > Date: Wed, 9 Jan 2002 18:11:16 +0100
> > From: "J. Henning Schwentner" <hschwentner AT yahoo DOT com>
> > To: cygwin AT cygwin DOT com
> > 
> > Am Montag, 7. Januar 2002 17:49 schrieben Sie:
> > > Jon Leichter wrote:
> > > > - Using CC="gcc -mno-cygwin" is good for compiling, but 
> it's bad for GNU
> > > > Libtool, as I have mentioned. I use a wrapper script: 
> CC=mgcc. What do
> > > > you think of this Earnie?
> > >
> > > Your wrapper script is a good idea but has the wrong name 
> as has been
> > > pointed out already.  It needs to be named 
> i386-pc-mingw32-gcc and a
> > > copy as mingw32-gcc so that when specifying the --host=mingw32 or
> > > --host=i386-pc-mingw32 the configure script will find it 
> appropriately.
> > > Of course to do this you also need to do the same for the binutils
> > > binaries.
> > 
> > Do the binutils also support the -mno-cygwin switch? 
> 
> I'll leave that as an exercise for you to figure out.
> 
> > Or can the
> > 386-pc-mingw32-<binutilname> files be simple links to the 
> cygwin versions?
> > 
> 
> Yes, simply symlink will do.

So the simlink is not needed at all: if autotools don't find, say
"i386-pc-mingw32-ar", they'll look for plain "ar" and use it. So no need to
mind with these symlinks. Just creating the script/exec i386-pc-mingw32-gcc
will be enough (and a i386-pc-mingw32-g++ link to it when we get a mingw32
libstdc++ of course :)).

Regards

--------------------------------------------
Bernard Dautrevaux
Microprocess Ingenierie
97 bis, rue de Colombes
92400 COURBEVOIE
FRANCE
Tel:	+33 (0) 1 47 68 80 80
Fax:	+33 (0) 1 47 88 97 85
e-mail:	dautrevaux AT microprocess DOT com
		b DOT dautrevaux AT usa DOT net
-------------------------------------------- 

--
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 -