This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [PATCH] Last toplevel bootstrap patch
- From: DJ Delorie <dj at redhat dot com>
- To: giovannibajo at libero dot it
- Cc: bonzini at gnu dot org, gcc-patches at gcc dot gnu dot org
- Date: Wed, 1 Sep 2004 08:59:56 -0400
- Subject: Re: [PATCH] Last toplevel bootstrap patch
- References: <413451D1.8030509@gnu.org> <02ed01c4900b$f1a2e100$bf4e2597@bagio>
> Great. Maybe now it is time to explain us poor mortarls what "top-level
> bootstrap" is... I admit I have absolutely *no clue* about it at all.
It's pretty simple. From the top, if you run "make bootstrap",
it used to do this:
make texinfo - once
make bison - once
make libiberty - once
make gas - once
make ld - once
make gcc - once, twice, three times
Now it does this:
make texinfo, bison, libiberty, gas, ld, gcc
once
make texinfo, bison, libiberty, gas, ld, gcc
twice
make texinfo, bison, libiberty, gas, ld, gcc
three times
The difference is that with toplevel bootstrap, ALL the toplevel
directories get rebuilt with the just-built tools, not just the gcc
directory.
It's like doing "configure; make; make install" three times in a row,
using the just-installed tools for each next build.