diff options
| author | Greg Schafer <greg@linuxfromscratch.org> | 2003-09-23 05:54:49 +0000 |
|---|---|---|
| committer | Greg Schafer <greg@linuxfromscratch.org> | 2003-09-23 05:54:49 +0000 |
| commit | ccaabde9fa61eef979216eb0b68c4ffae54d97a8 (patch) | |
| tree | abc6cedad379d67e095e00306b83f2470c03c034 /chapter05/gcc-pass2-inst.xml | |
| parent | 990ba6b8b89ff0170273e073f29577d580495fc4 (diff) | |
Chapter 5 - GCC Pass 2: Insert note to rerun the previously ran sanity check.
git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@2871 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
Diffstat (limited to 'chapter05/gcc-pass2-inst.xml')
| -rw-r--r-- | chapter05/gcc-pass2-inst.xml | 12 |
1 files changed, 9 insertions, 3 deletions
diff --git a/chapter05/gcc-pass2-inst.xml b/chapter05/gcc-pass2-inst.xml index 02f342f5c..74ef57c8c 100644 --- a/chapter05/gcc-pass2-inst.xml +++ b/chapter05/gcc-pass2-inst.xml @@ -25,7 +25,7 @@ are able to resolve the issue. You can consult the LFS Wiki at get PTYs working.</para> <note><para>It's worth pointing out that the GCC test suite we run in this -section is considered not as critical as the one we run in Chapter 6.</para></note> +section is considered not as important as the one we run in Chapter 6.</para></note> <para>Unpack all three GCC tarballs (-core, -g++, and -testsuite) in one and the same working directory. They will all unfold into a single <filename>gcc-&gcc-version;/</filename> @@ -77,9 +77,15 @@ variables that override the default optimization flags.</para> <para>Compile the package:</para> <para><screen><userinput>make</userinput></screen></para> + <para>There is no need to use the <userinput>bootstrap</userinput> target now, -as the compiler we're using to compile this GCC has been built from the exact -same sources.</para> +as the compiler we're using to compile this GCC was built from the exact same +version of the GCC sources we used earlier.</para> + +<note><para>At this point it is strongly recommended to repeat the sanity check +we performed earlier in the chapter. Refer back to the "Locking in" Glibc section +and repeat the check. If the results are wrong then most likely, you forgot to +apply the abovementioned GCC Specs patch.</para></note> <para>Test the results:</para> |