Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
Message-ID: <05b801c19a3f$20199850$0200a8c0@lifelesswks>
From: "Robert Collins" <robert.collins@itdomain.com.au>
To: "Jon Leichter" <jon@symas.com>
Cc: <cygwin@cygwin.com>
References: <DLEBJKNCNLJEDKMKICHGEENOCBAA.jon@symas.com>
Subject: Re: Compiling apps to Mingw32 with cygwin
Date: Fri, 11 Jan 2002 12:27:24 +1100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
X-OriginalArrivalTime: 11 Jan 2002 01:27:23.0597 (UTC) FILETIME=[1EF367D0:01C19A3F]

----- Original Message -----
From: "Jon Leichter" <jon@symas.com>
To: "Robert Collins" <robert.collins@itdomain.com.au>
Cc: <cygwin@cygwin.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
understanding
> of --build, --host, and --target (which I'm incredibly grateful for
and
> happy about).
>
> I have returned to working with OpenLDAP. The configure script is
generated
> 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,
which
> is what I want. It does.
>
> First, some questions:
>
> - What is correct: i386-pc-mingw32 or i686-pc-mingw32? If one is
correct,
> 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
equate
> "mingw32" as "i386-unknown-mingw32". Why?
>
> - Is there a plan to get "32" from "mingw32", i.e. "mingw"? Of course,
that
> won't be useful with old projects that still need the "32" to be
present...
> :(
>
> ===
>
> Now my results:
>
> - I never see configure look for i686-pc-mingw32-gcc. It merely picks
up
> '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 :}.

Rob


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

