code is syntactically correct (e.g., that you did not use GCC extensions
by mistake), and avoids spurious bootstrap comparison
failures@footnote{Except if the compiler was buggy and miscompiled
- some of the files that were not modified. In this case, it's best
- to use @command{make restrap}.}.
+some of the files that were not modified. In this case, it's best
+to use @command{make restrap}.}.
Other targets available from the top level include:
For each package that is bootstrapped, rename directories so that,
for example, @file{gcc} points to the stage@var{N} GCC, compiled
with the stage@var{N-1} GCC@footnote{Customarily, the system compiler
- is also termed the @file{stage0} GCC.}.
+is also termed the @file{stage0} GCC.}.
You will invoke this target if you need to test or debug the
stage@var{N} GCC@. If you only need to execute GCC (but you need