delorie.com/archives/browse.cgi | search |
Mailing-List: | contact cygwin-help AT cygwin DOT com; run by ezmlm |
List-Subscribe: | <mailto:cygwin-subscribe AT cygwin DOT com> |
List-Archive: | <http://sources.redhat.com/ml/cygwin/> |
List-Post: | <mailto:cygwin AT cygwin DOT com> |
List-Help: | <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs> |
Sender: | cygwin-owner AT cygwin DOT com |
Mail-Followup-To: | cygwin AT cygwin DOT com |
Delivered-To: | mailing list cygwin AT cygwin DOT com |
Reply-To: | <nhv AT cape DOT com> |
From: | "Norman Vine" <nhv AT cape DOT com> |
To: | <cygwin AT cygwin DOT com> |
Subject: | RE: [avail for test] libtool-devel-20030216-1 |
Date: | Tue, 18 Feb 2003 22:17:28 -0500 |
Message-ID: | <EKEJIKAILPONGGENMBGAMEENCJAA.nhv@cape.com> |
MIME-Version: | 1.0 |
X-Priority: | 3 (Normal) |
X-MSMail-Priority: | Normal |
In-Reply-To: | <20030219023640.GE26147@redhat.com> |
X-MimeOLE: | Produced By Microsoft MimeOLE V6.00.2800.1106 |
Importance: | Normal |
X-Virus-Scanned: | Cape.Com VirusScan, no known virus found |
Christopher Faylor writes: > > On Tue, Feb 18, 2003 at 09:26:12PM -0500, Charles Wilson wrote: > >You can work around this with wrapper scripts (e.g. 'mgcc' contains > >'exec gcc -mno-cygwin $*') but that's non standard. > > However, it could easily be standard. I could include a > i686-pc-mingw32-gcc > and a i686-pc-mingw-ld in the gcc distribution. And, I could also alias > all of the i686-pc-cygwin-* tools to i686-pc-mingw32-*. That > would provide > the equivalent of a cross compilation environment for cygwin. > > Then you just have to say > > configure --host=i686-pc-mingw32 --target=i686-pc-mingw32 > --build=i686-pc-cygwin > > and you bypass the arbitrary distinction of having a whole build system, > based on cygwin which exists just so that uname returns 'mingw', > or whatever. > > (Yes, I know that MSYS does other things, too, but this does get rid of > the requirement of using MSYS just to make it easy to use > autoconf/libtool) I use a slightly different technique I maintain a separate /$MINGW development tree within my $CYGWIN tree and make sure that $MINGW/bin comes before /bin in $PATH then ./configure --prefix=$MINGW --host=mingw seems to work fine from a bash shell Norman -- 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/
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |