From: Rene Rebe <rene.rebe@gmx.net>
To: eager@eagercon.com
Cc: pkoning@equallogic.com, drow@mvista.com, gcc@gcc.gnu.org,
rock-linux@rocklinux.org
Subject: Re: building a gcc-3.3-prerelease cross-compiler
Date: Tue, 13 May 2003 22:14:00 -0000 [thread overview]
Message-ID: <20030513.235807.838022001.rene.rebe@gmx.net> (raw)
In-Reply-To: <3EC156DF.2020201@eagercon.com>
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
next prev parent reply other threads:[~2003-05-13 22:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-12 12:00 Rene Rebe
2003-05-12 14:22 ` Daniel Jacobowitz
2003-05-12 16:51 ` Rene Rebe
2003-05-12 16:59 ` Paul Koning
2003-05-12 19:24 ` Rene Rebe
2003-11-05 14:12 ` Rene Rebe
2003-05-13 15:46 ` Michael Eager
2003-05-13 16:07 ` Rene Rebe
2003-05-13 18:56 ` Michael Eager
2003-05-13 19:44 ` Rene Rebe
2003-05-13 20:34 ` Michael Eager
2003-05-13 22:14 ` Rene Rebe [this message]
2003-05-12 17:04 ` Joseph S. Myers
2003-05-12 17:13 ` Daniel Jacobowitz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030513.235807.838022001.rene.rebe@gmx.net \
--to=rene.rebe@gmx.net \
--cc=drow@mvista.com \
--cc=eager@eagercon.com \
--cc=gcc@gcc.gnu.org \
--cc=pkoning@equallogic.com \
--cc=rock-linux@rocklinux.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).