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: <3C42E078.779D2FAA@yahoo.com>
Date: Mon, 14 Jan 2002 08:43:20 -0500
From: Earnie Boyd <earnie_boyd AT yahoo DOT com>
X-Mailer: Mozilla 4.77 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Robert Collins <robert DOT collins AT itdomain DOT com DOT au>
CC: Jon Leichter <jonleichter AT mediaone DOT net>, hschwentner AT yahoo DOT com,
   cygwin AT cygwin DOT com
Subject: Re: Compiling apps to Mingw32 with cygwin
References: <CIENIMJIOHKBPJEFFFOBIEIJCBAA DOT jonleichter AT mediaone DOT net> <3C407AFB DOT DC2871B5 AT yahoo DOT com> <04fc01c19bc0$b5c97730$0200a8c0 AT lifelesswks>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit



Robert Collins wrote:
> 
> ----- Original Message -----
> From: "Earnie Boyd" <earnie_boyd AT yahoo DOT com>
> > 1) `gcc -mno-cygwin' is not a cross compile.
> > 2) it is possible to emulate a cross build system using a scripted
> `gcc
> > -mno-cygwin' and symlinks.
> > 3) `gcc -mno-cygwin' switches the build environment from Cygwin to
> > MinGW.
> 
> Earnie, on 3) I believe we have a terminology problem. gcc -mno-cygwin
> changes the _build target_ to mingw32, no the build _environment_.
> 
> In the context of configure scripts the build _environment_ is the
> platform hosting the running script, and doing the compilation - that is
> cygwin.
> 

You need to narrow your thinking to GCC and binutils the processes of
consequence.  You only need to specify the triplet because config.guess
guesses wrong based on the value of `uname -s'.  The cygwin binutils as
named will produce executables that use MSVCRT.DLL instead of
CYGWIN1.DLL without having to do anything special with their names or
output.  So, my statement stands based on what happens with GCC, you're
switching the build environment.

> > > You said this was wrong. To be consisent with future behavior, it
> seems that
> > > I must specify build. So if you're suggesting that I'm not
> cross-compiling,
> > > then it would be:
> > >
> > >         $ env CC=mgcc
> ./configure --host=i686-pc-mingw32 --build=i686-pc-mingw32
> > >
> >
> > This is what I would do.
> 
> IMO this is wrong (wrong build value) - see my comment earlier.
> 

No, you're not doing a cross build, therefore I've stated the correct
switches.

Earnie.

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


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