This is the mail archive of the
mailing list for the Cygwin project.
Re: Compiling apps to Mingw32 with cygwin
- From: Earnie Boyd <earnie_boyd at yahoo dot com>
- To: CU List <Cygwin at Cygwin dot Com>
- Date: Fri, 11 Jan 2002 07:42:21 -0500
- Subject: Re: Compiling apps to Mingw32 with cygwin
- References: <3C3EDCA7.C40E3CD6@yahoo.com>
> Subject: Re: Compiling apps to Mingw32 with cygwin
> Date: Fri, 11 Jan 2002 13:25:17 +1100
> From: "Robert Collins" <email@example.com>
> To: "Jon Leichter" <firstname.lastname@example.org>
> CC: <email@example.com>
> ----- Original Message -----
> From: "Jon Leichter" <firstname.lastname@example.org>
> > > See above why it doesn't. mingw != cygwin :}.
> > If 'build' WERE to be tested automatically, independent to 'host', it
> > come up with 'i686-pc-cygwin'. Thus, we'd effectively end up with the
> > line you specified above. So that does work, right? Or are you trying
> > confuse me again??? :)
> What doesn't kill us makes us stronger. IF build were tested correctly
> yes. But it's not currently tested - it defaults to host IFF host is
This rule is changed for 2.50 and greater. Build no longer takes on the
value of host and you're warned about this when specifying --host
without specifying --build. IIRC, if you specify build without host
then host takes on the value of build but I may be wrong on this point.
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