Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT sourceware DOT cygnus DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT sourceware DOT cygnus DOT com>
List-Archive: <http://sourceware.cygnus.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sourceware DOT cygnus DOT com>
List-Help: <mailto:cygwin-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender: cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com
Message-ID: <19990929190731.872.rocketmail@web128.yahoomail.com>
Date: Wed, 29 Sep 1999 12:07:31 -0700 (PDT)
From: Earnie Boyd <earnie_boyd AT yahoo DOT com>
Reply-To: earnie_boyd AT yahoo DOT com
Subject: Re: Using mingw32 to build cross-tools
To: "M. R. Brown" <marcusb AT csd DOT uwm DOT edu>
Cc: cygwin users <cygwin AT sourceware DOT cygnus DOT com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

--- "M. R. Brown" <marcusb AT csd DOT uwm DOT edu> wrote:
> A little off-topic, but...
-8<-
> build scripts run under, well, cygwin.  I've tried mixing mingw32 and
> cygwin beta 19 in the past and all hell broke loose.  If anyone has tried
> this, let me know.
-8<-

As I've said before, I do it now.  What you have to remember is that the
Mingw32 GCC toolset has no idea about the cygwin mounts.  Therefore you have to
use the environment variables to tell GCC where to find specs, includes and
libraries.  I've been doing this since B18 with _NO_ problems.

What problems have you had?


=====
Earnie Boyd <mailto:earnie_boyd AT yahoo DOT com>

Newbies, please visit
<http://www.freeyellow.com/members5/gw32/index.html>

(If you respond to the list, then please don't cc me)
__________________________________________________
Do You Yahoo!?
Bid and sell for free at http://auctions.yahoo.com

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com