From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8020 invoked by alias); 10 Jan 2002 21:43:45 -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 7993 invoked from network); 10 Jan 2002 21:43:42 -0000 Received: from unknown (HELO itdomain003.itdomain.net.au) (203.63.157.208) by sources.redhat.com with SMTP; 10 Jan 2002 21:43:42 -0000 Received: from lifelesswks ([203.51.0.200]) by itdomain003.itdomain.net.au with Microsoft SMTPSVC(5.0.2195.3779); Fri, 11 Jan 2002 08:43:41 +1100 Message-ID: <047601c19a1f$df92d450$0200a8c0@lifelesswks> From: "Robert Collins" To: Cc: References: Subject: Re: Compiling apps to Mingw32 with cygwin Date: Thu, 10 Jan 2002 13:43:00 -0000 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: 10 Jan 2002 21:43:41.0200 (UTC) FILETIME=[DE942900:01C19A1F] X-SW-Source: 2002-01/txt/msg00671.txt.bz2 ----- Original Message ----- From: "Jon Leichter" I hope I don't repeat anything from this thread, I've only been scanning it lightly. .. > obvious to me that unless you're building a project with a configure script > built by an up-to-date version of autoconf, none of what you have suggested > will work. Note that the approach I suggested will work in either case, WITH > THE POSSIBLE EXCEPTION (as you have stated) that one runs into trouble > if --build and --target are not specified as well. Autoconf 2.13 supports these options - so the configure script doesn't need to be *that* up to date. However, the script needs AC_CANONICAL_BUILD AC_CANONICAL_HOST (and if the package generates platform specific output (ie it's an assembler/compiler etc) AC_CANONICAL_TARGET in the configure.in. You may need to add the relevant macros and run autoconf again. As for --build, it is automatically detected as long as AC_CANONICAL_BUILD is in the script. You may get a warning == configure: WARNING: If you wanted to set the --build type, don't use --host. If a cross compiler is detected then cross compile mode will be used. == This warning is safe IFF you have a cross compiler. > This spawns another associated topic. What are the right values for the > triplets (in CURRENT autoconf)? If you're building MinGW binaries in a > Cygwin-hosted environment, it seems to me that you should ONLY > specify --target=i686-pc-mingw32 and let the other two switches resolve No. Specify --host. The meaning is clearly documented in the autoconf documentation. For clarity: build - what OS the compilation is running on.. host - what OS the binaries created should run on. target - what OS the binaries created should target their output to. > Note that I have tried to only use the --target switch in my projects, > opposed to the --host switch. However, in OpenLDAP and the other related > projects, NONE of the configure scripts handle these switches correctly. I > found that using --host was the best solution for these projects. --target being the wrong switch, I'm not surprised it didn't do what you wanted :}. 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/