From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15593 invoked by alias); 11 Jan 2002 02:11:49 -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 15544 invoked from network); 11 Jan 2002 02:11:45 -0000 Received: from unknown (HELO illustrious.cnchost.com) (207.155.252.7) by sources.redhat.com with SMTP; 11 Jan 2002 02:11:45 -0000 Received: from piano (adsl-66-120-57-93.dsl.lsan03.pacbell.net [66.120.57.93]) by illustrious.cnchost.com id VAA18140; Thu, 10 Jan 2002 21:11:43 -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 18:11: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: <05ea01c19a42$907377d0$0200a8c0@lifelesswks> Importance: Normal X-SW-Source: 2002-01/txt/msg00712.txt.bz2 Thus... returning to the ORIGINAL topic of this thread... I had recommended the following to the OP: $ env CC=mgcc ./configure --host=i686-pc-mingw32 My new understanding of switches gives me new perspective. 'build' and 'target' will pickup the value of 'host'. In this context, you're telling configure that the host == build == MinGW. I've said before that MinGW in Cygwin is a loose cross-compile. So, it seems to me that this configuration is ok, especially since 'host' binaries CAN successfully run in the 'build' environment. It seems to me that my original solution is suitable whether or not one's configure script was written "properly" and was built with the latest autoconf. We agreed that as of today that 'build', if not specified, gets the value of 'host'. Even if this were to change, i.e. 'build' gets checked for automatically, my solution STILL works. In this case, it would be a cross compile, but it should still work. This leads one to draw the following conclusions: - If one uses the --host, --build, and --target switches properly, he is not guaranteed that the configure script will work correctly. It will only work correctly IFF an up-to-date autoconf generated the script AND the switches were utilized correctly in configure.in. - If one uses my method posted above, it will work most (if not all) of the time. So, it may not be "proper", but it WILL work. This whole thread went off on a tangent suggesting that my solution was wrong. So tell me. If my solution works more often than the "proper" one, how is it wrong? Jon > -----Original Message----- > From: Robert Collins [mailto:robert.collins@itdomain.com.au] > Sent: Thursday, January 10, 2002 5:52 PM > To: Jon Leichter > Cc: cygwin@cygwin.com > Subject: Re: Compiling apps to Mingw32 with cygwin > > ----- Original Message ----- > From: "Jon Leichter" > > > AC_CHECK_TOOL checks for tools with a ${host} prefix. AC_CHECK_PROG > does > > not. > > > > In my opinion, this serves as another example that one cannot count on > a > > configure script being up-to-date. > > Ouchies. I agree - yet another reason for cygwin ports to be updated by > the maintainer :}. > > Rov > > > -- 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/