From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13453 invoked by alias); 6 Jan 2002 17:55:04 -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 13015 invoked from network); 6 Jan 2002 17:54:55 -0000 Received: from unknown (HELO lsmls01.we.mediaone.net) (24.130.1.20) by sources.redhat.com with SMTP; 6 Jan 2002 17:54:55 -0000 Received: from neo (we-24-130-210-97.we.mediaone.net [24.130.210.97]) by lsmls01.we.mediaone.net (8.11.4/8.11.3) with SMTP id g06Hrep24762; Sun, 6 Jan 2002 09:53:40 -0800 (PST) From: "Jon Leichter" To: "J. Henning Schwentner" Cc: Subject: RE: Compiling apps to Mingw32 with cygwin Date: Sun, 06 Jan 2002 09:55:00 -0000 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" 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) In-Reply-To: <200201061357.IAA27856@zealous.cnchost.com> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Importance: Normal X-SW-Source: 2002-01/txt/msg00233.txt.bz2 For the most part, I agree with you. Autoconf and Libtool should be fixed. The motto of the groups seems to be: "patches gratefully accepted". Thus, unless you, me, or someone else that uses Cygwin GCC for MinGW wants to make these changes, I wouldn't count on them coming around any time soon. One other point: AFAIK, the cross-compiling feature of autoconf, i.e. --host, --build, --target, is not an automated feature. That is, it's up to the configure.in script writer to use these switches appropriately. I have ran many configure scripts in the Cygwin environment. I have just about never seen a configure script use these switches correctly (where "correctly" is based on the definition of these switches in the autoconf documentation). Thus, for this issue, you can't look for a "fix" in autoconf. It's about configure.in script writers doing the right thing. This, of course, means that there must be a separate "fix" for each project that is not doing the right thing. Of course, if a script that you're using is coming out of a OpenSource project, then again, one is free to supply patches... Jon > -----Original Message----- > From: cygwin-owner@cygwin.com [mailto:cygwin-owner@cygwin.com]On Behalf > Of J. Henning Schwentner > Sent: Sunday, January 06, 2002 5:57 AM > To: cygwin@cygwin.com > Subject: Re: Compiling apps to Mingw32 with cygwin > > Thanks for your quick help, this works nice! > > But, it is a bit difficult. I think ideally configure should detect > --host=mingw32 --build=cygwin and in this case should add --mno-cygwin to > CFLAGS and CPPFLAGS (and do something to fix libtool). > > I am not sure if this is a bit off topic, maybe this sould be > posted to the > autoconf list. > > Regards, > Henning > > _________________________________________________________ > Do You Yahoo!? > Get your free @yahoo.com address at http://mail.yahoo.com > > > -- > 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/ > -- 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/