From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25546 invoked by alias); 11 Jan 2002 01:19:38 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Received: (qmail 25494 invoked from network); 11 Jan 2002 01:19:37 -0000 Received: from unknown (HELO illustrious.cnchost.com) (207.155.252.7) by sources.redhat.com with SMTP; 11 Jan 2002 01:19:37 -0000 Received: from piano (adsl-66-120-57-93.dsl.lsan03.pacbell.net [66.120.57.93]) by illustrious.cnchost.com id UAA21908; Thu, 10 Jan 2002 20:19:30 -0500 (EST) [ConcentricHost SMTP Relay 1.14] Errors-To: From: "Jon Leichter" To: "Robert Collins" Cc: Subject: RE: Compiling apps to Mingw32 with cygwin Date: Thu, 10 Jan 2002 17:19:00 -0000 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: <054701c19a36$d3d8b230$0200a8c0@lifelesswks> Importance: Normal X-SW-Source: 2002-01/txt/msg00695.txt.bz2 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? - I DO see configure look for ${host} binutils, i.e. i686-pc-mingw32-, but since I don't have symlinks, it finds unprefixed versions of the tools. This, of course, is what I want to happen. 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/