public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Giovanni Bajo" <rasky@develer.com>
To: "Paolo Bonzini" <bonzini@gnu.org>
Cc: <gcc@gcc.gnu.org>
Subject: Re: toplevel bootstrap (stage 2 project)
Date: Wed, 22 Jun 2005 19:00:00 -0000	[thread overview]
Message-ID: <055301c5775c$9c133c10$bf03030a@trilan> (raw)
In-Reply-To: <d9boea$m79$1@sea.gmane.org>

Paolo Bonzini <bonzini@gnu.org> wrote:

> To recap, toplevel bootstrap has several aims, including:
>[...]

I suggest you to add this to the Wiki.

> To enable toplevel bootstrap, just configure with --enable-bootstrap.
> Then, "make" will do more or less what "make bubblestrap" used to do:

What does "./configure --enable-botstrap; make bootstrap" do?

> It supports all the bells and whistles like bubblestraps and restageN,
> which help during development.  "make restrap" is not supported. "make
> restageN" is called "make all-stageN", and there is also "make
> all-stageN-gcc" to rebuild gcc only.

It would help also if you add to the wiki explanation of what exactly all
these options do. Especially bubblestrap vs quickstrap vs restrap.

Thanks!
-- 
Giovanni Bajo

  reply	other threads:[~2005-06-22 19:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-22 13:25 CFT: " Paolo Bonzini
2005-06-22 19:00 ` Giovanni Bajo [this message]
2005-06-23  7:27   ` Paolo Bonzini
2005-06-24 23:11   ` Gerald Pfeifer
2005-06-28  9:43     ` Giovanni Bajo
2005-06-28 13:27       ` Daniel Berlin
2005-06-28 17:00         ` Giovanni Bajo
2005-06-22 21:35 ` CFT: " Geoffrey Keating
     [not found] ` <m364w3hei3.fsf@localhost.localdomain>
2005-07-05  9:58   ` Paolo Bonzini
2005-08-06 11:47 ` Joseph S. Myers

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='055301c5775c$9c133c10$bf03030a@trilan' \
    --to=rasky@develer.com \
    --cc=bonzini@gnu.org \
    --cc=gcc@gcc.gnu.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).