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
Date: Wed, 29 Sep 1999 14:41:53 -0500 (CDT)
From: "M. R. Brown" <marcusb AT csd DOT uwm DOT edu>
To: cygwin AT sourceware DOT cygnus DOT com
Subject: Re: Using mingw32 to build cross-tools
In-Reply-To: <19990929190731.872.rocketmail@web128.yahoomail.com>
Message-ID: <Pine.OSF.3.96.990929142911.1615G-100000@alpha3.csd.uwm.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

I had a dual-environment setup similiar to the one you detail on your
site.  I had d:\root\cygwin-b19 and d:\root\mingw32 and I used `regedit /s
cygwin-root.reg' and `regedit /s mingw32-root.reg' to dynamically change
the mount points for both of my startup batch files.  I guess the problems
I had stemmed from b19 not being able to cross correctly, because I would
get something like "File access error..." when make executed libtool to
link binutils.  And that was just under cygwin-b19 (FYI, I was trying to
cross binutils-2.9.5.0.12). Unfortunately I don't remember what happened
when I tried it under mingw32.  I guess my focus is not on mixing mingw32
and cygwin (cause I can do that), but on using mingw32 to build
cross-tools.  It looks like you answered most of my question, after work
I'll give it another whirl. 

Marcus

P.S. Earnie, sorry about the blank e-mail, I'm on a slow link and
accidentally hit the wrong key :)

On Wed, 29 Sep 1999, Earnie Boyd wrote:

> --- "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
> 
> 
> 



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