Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
X-Authentication-Warning: hp2.xraylith.wisc.edu: khan owned process doing -bs
Date: Fri, 9 Mar 2001 22:26:35 -0600 (CST)
From: Mumit Khan <khan AT NanoTech DOT Wisc DOT EDU>
To: cygwin AT cygwin DOT com
Subject: Re: cross compiler for Cygwin
In-Reply-To: <20010309225502.A3200@redhat.com>
Message-ID: <Pine.HPP.3.96.1010309222131.14734C-100000@hp2.xraylith.wisc.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Fri, 9 Mar 2001, Christopher Faylor wrote:

> Or, maybe the misinformation you're referring to is even more basic than
> "How do I build a cross-compiler?"  It does seem like a lot of people
> expect to get cross-compilation out-of-the-box.

We would hope that someday it will build out of the box! Unfortunately, the 
current setup requires a bit of digging in, and for some reason, it seems 
to be a daunting task for many.

That's one great thing about the one-tree build that RedHat/Cygnus uses,
no hassle builds for a myriad a of host-target combos. And that's why
embedded system developers pay for commercial support, the cost of which
may seem atrocious when you first see it, but you soon find out that it's 
well worth it.

Regards,
Mumit



--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple