This is the mail archive of the crossgcc@sources.redhat.com mailing list for the crossgcc project.

See the CrossGCC FAQ for lots more information.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Building a cross-toolchain from scratch

From: "E. Weddington" <eric at umginc dot net>
To: Peter Barada <pbarada at mail dot wm dot sps dot mot dot com>
Cc: crossgcc at sources dot redhat dot com
Date: Tue, 03 Jun 2003 10:47:49 -0600
Subject: Re: Building a cross-toolchain from scratch
References: <3EDC6F6A.1060008@luukku.com> (message from Kai Ruottu on Tue, 03 Jun 2003 12:50:34 +0300)

On 3 Jun 2003 at 11:50, Peter Barada wrote:

> >	alpha, arm, hppa, i386, ia64, m68k, mips, mipsel,
> >	powerpc, s390, s390x, sparc, sparc64
> 
> And how do the sh, ppc64, m68k folks get a build, not to mention
> anyone that trying to develop for a *new* architecture?
> 
> I want to track the active sources (CVS head) for various parts of the
> toolchain so I can report failures *before* they get into a release.
> 
> That's impossible if I have to wait for a 'prebuilt' glibc to show up....
> 
> We *need* a method that relies only on a working C compiler so we can
> bootstrap for *every* target.

Which targets are you interested in? Just the ones that glibc supports?: 
<http://www.gnu.org/software/libc/porting.html> 

Eric


------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com

Follow-Ups:
- Re: Building a cross-toolchain from scratch
  - From: Peter Barada

References:
- Re: Building a cross-toolchain from scratch
  - From: Kai Ruottu
- Re: Building a cross-toolchain from scratch
  - From: Peter Barada

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]