gronod/lfs
1
0
Fork 0
mirror of https://git.linuxfromscratch.org/lfs.git synced 2025-06-20 04:09:21 +01:00
Code Issues Packages Projects Releases Wiki Activity

Fix my stuffup re placement of repeat sanity checks. What was I thinking?

Browse Source 
git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@2926 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
This commit is contained in:
Greg Schafer 2003-10-06 01:03:26 +00:00
parent 5765b1dfab
commit 076ddfe40d
3 changed files with 11 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
chapter05/binutils-pass1-inst.xml
View File

@ -78,7 +78,7 @@ This option rebuilds everything in the <filename>ld</filename> subdirectory.
Specifying the LIB_PATH makefile variable on the command line allows us to Specifying the LIB_PATH makefile variable on the command line allows us to
override the default value and have it point to our temporary tools location. override the default value and have it point to our temporary tools location.
The value of this variable specifies the linker's default library search path. The value of this variable specifies the linker's default library search path.
You'll see how this preparation is utilised later on in the You'll see how this preparation is used later on in the
chapter.</para></listitem> chapter.</para></listitem>
</itemizedlist> </itemizedlist>

10
chapter05/gcc-pass2-inst.xml
View File

@ -107,11 +107,6 @@ needed to ensure that both C and C++ compilers are built.</para></listitem>
as the compiler we're using to compile this GCC was built from the exact same 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> 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> <para>Test the results:</para>
<para><screen><userinput>make -k check</userinput></screen></para> <para><screen><userinput>make -k check</userinput></screen></para>
@ -157,5 +152,10 @@ to continue on.</para>
<para><screen><userinput>make install</userinput></screen></para> <para><screen><userinput>make install</userinput></screen></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>
</sect2> </sect2>

10
chapter06/gcc-inst.xml
View File

@ -43,11 +43,6 @@ cd ../gcc-build</userinput></screen></para>
<para><screen><userinput>make</userinput></screen></para> <para><screen><userinput>make</userinput></screen></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 "Re-adjusting the
toolchain" section and repeat the check. If the results are wrong then most
likely, you erroneously applied the GCC Specs patch from Chapter 5.</para></note>
<para>Test the results, but don't stop at errors (you'll remember the few <para>Test the results, but don't stop at errors (you'll remember the few
known ones):</para> known ones):</para>
@ -72,4 +67,9 @@ compiler. To satisfy those packages, create a symlink:</para>
<para><screen><userinput>ln -s gcc /usr/bin/cc</userinput></screen></para> <para><screen><userinput>ln -s gcc /usr/bin/cc</userinput></screen></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 "Re-adjusting the
toolchain" section and repeat the check. If the results are wrong then most
likely, you erroneously applied the GCC Specs patch from Chapter 5.</para></note>
</sect2> </sect2>