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: "Jon Leichter" <jon at symas dot com>
- Cc: <cygwin at cygwin dot com>
- Date: Fri, 11 Jan 2002 12:27:24 +1100
- Subject: Re: Compiling apps to Mingw32 with cygwin
- References: <DLEBJKNCNLJEDKMKICHGEENOCBAA.email@example.com>
----- Original Message -----
From: "Jon Leichter" <firstname.lastname@example.org>
To: "Robert Collins" <email@example.com>
Sent: Friday, January 11, 2002 12:20 PM
Subject: RE: Compiling apps to Mingw32 with cygwin
> Ok. I need to return to asking some questions with my new
> of --build, --host, and --target (which I'm incredibly grateful for
> happy about).
> I have returned to working with OpenLDAP. The configure script is
> with autconf-2.13.1. It uses AC_CANONICAL_SYSTEM, which you say is
> deprecated. I assume, however, that it still works to some extent.
> I tried to configure with the following:
> $ ./configure --build=i686-pc-cygwin --host=i686-pc-mingw32
> I've left --target off, since I know it will get the value of --host,
> is what I want. It does.
> First, some questions:
> - What is correct: i386-pc-mingw32 or i686-pc-mingw32? If one is
> why? If both are correct, how does one decide which one to use?
> - I notice that if I merely use --host=mingw32, config.guess will
> "mingw32" as "i386-unknown-mingw32". Why?
> - Is there a plan to get "32" from "mingw32", i.e. "mingw"? Of course,
> won't be useful with old projects that still need the "32" to be
> Now my results:
> - I never see configure look for i686-pc-mingw32-gcc. It merely picks
> 'gcc'. Any ideas why?
Do you have an accessible i686-pc-mingw32-gcc ?
have a look at the configure script - it may provide some clues :}.
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html