Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com From: "Jon Leichter" To: "Robert Collins" Cc: Subject: RE: Compiling apps to Mingw32 with cygwin Date: Thu, 10 Jan 2002 17:33:02 -0800 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700 In-Reply-To: <05b801c19a3f$20199850$0200a8c0@lifelesswks> Importance: Normal > -----Original Message----- > From: Robert Collins [mailto:robert DOT collins AT itdomain DOT com DOT au] > Sent: Thursday, January 10, 2002 5:27 PM > To: Jon Leichter > Cc: cygwin AT cygwin DOT com > Subject: Re: Compiling apps to Mingw32 with cygwin > > > ----- Original Message ----- > From: "Jon Leichter" > To: "Robert Collins" > Cc: > 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 > Sorry... I left that out. Yes, I do have an accessible i686-pc-mingw32-gcc, and I am looking at the configure script. It just searches for gcc. It doesn't bother to look for the prefixed tool. Jon -- 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/