building a gcc-3.3-prerelease cross-compiler

[Rene Rebe]

Hi,

On: Tue, 13 May 2003 13:34:39 -0700,
    Michael Eager <eager@eagercon.com> wrote:

> Rene Rebe wrote:

> > Could you elaborate on the problem that appears to be overlooked?
> 
> I occasionally have a need to build a toolchain for a new architecture
> or new variant.  After building binutils, the first step is to build
> a bootstrap compiler.  Once I have that compiler, I can build glibc.
> After building glibc, I build a complete gcc.  Both versions of gcc,
> the bootstrap and the final, are built from the same sources.

Yes we do so.

> In your scheme, you assume that the bootstrap has been done.  Also
> the compiler you use to build glibc is potentially one revision back
> from your final compiler.

Nope. Our stage-0 is only creating the bootstrap toolchain, after that
the glibc and other packages are build.

> When you are working with one architecture, and repeatedly building
> for that architecture, then this not a problem.  But if you are building
> tools for different architectures, or a new architecture, or you want to
> make the entire process explicit, the bootstrap process should be explicit.

Yes - but this is how we do ;-) I even currently configure an
regression tester to log and ensure those cross builds are working
correctly. Might also be useful for the gcc folks, when I also log cvs
HEAD checkouts.

Sincerely,
  René Rebe
    - ROCK Linux stable release maintainer

--  
René Rebe - Europe/Germany/Berlin
  rene@rocklinux.org rene.rebe@gmx.net
http://www.rocklinux.org http://www.rocklinux.org/people/rene       
http://gsmp.tfh-berlin.de/gsmp http://gsmp.tfh-berlin.de/rene