This is the mail archive of the
mailing list for the Cygwin project.
Re: Compiling apps to Mingw32 with cygwin
- From: "Robert Collins" <robert dot collins at itdomain dot com dot au>
- To: "Earnie Boyd" <earnie_boyd at yahoo dot com>,"Jon Leichter" <jonleichter at mediaone dot net>
- Cc: <hschwentner at yahoo dot com>,<cygwin at cygwin dot com>
- Date: Sun, 13 Jan 2002 10:27:31 +1100
- Subject: Re: Compiling apps to Mingw32 with cygwin
- References: <CIENIMJIOHKBPJEFFFOBIEIJCBAA.firstname.lastname@example.org> <3C407AFB.DC2871B5@yahoo.com>
----- Original Message -----
From: "Earnie Boyd" <email@example.com>
> 1) `gcc -mno-cygwin' is not a cross compile.
> 2) it is possible to emulate a cross build system using a scripted
> -mno-cygwin' and symlinks.
> 3) `gcc -mno-cygwin' switches the build environment from Cygwin to
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
> > You said this was wrong. To be consisent with future behavior, it
> > I must specify build. So if you're suggesting that I'm not
> > 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.
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html