diff options
| author | Greg Schafer <greg@linuxfromscratch.org> | 2003-10-07 06:00:35 +0000 |
|---|---|---|
| committer | Greg Schafer <greg@linuxfromscratch.org> | 2003-10-07 06:00:35 +0000 |
| commit | f861982929d526b7628fc1a6f19386c665f28e31 (patch) | |
| tree | 259c0150e454b1d186c75fb56f00fb9c3efe10a6 /chapter06/gcc-inst.xml | |
| parent | f57e3d1ad9e6bfe96ebf823be19da0e07d81d52b (diff) | |
Miscellaneous fixes and cleanups.
git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@2932 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
Diffstat (limited to 'chapter06/gcc-inst.xml')
| -rw-r--r-- | chapter06/gcc-inst.xml | 13 |
1 files changed, 9 insertions, 4 deletions
diff --git a/chapter06/gcc-inst.xml b/chapter06/gcc-inst.xml index a070808ea..14add7a8a 100644 --- a/chapter06/gcc-inst.xml +++ b/chapter06/gcc-inst.xml @@ -18,7 +18,7 @@ to unpack the GCC-core <emphasis>and</emphasis> the GCC-g++ tarball -- they will unfold into the same directory. You should likewise extract the GCC-testsuite package. The full GCC package contains even more compilers. Instructions for building these can be found at -<ulink url="&blfs-root;view/cvs/general/gcc.html"/>.</para> +<ulink url="&blfs-root;view/stable/general/gcc.html"/>.</para> <para><screen><userinput>patch -Np1 -i ../gcc-&gcc-nofixincludes-patch-version;.patch patch -Np1 -i ../gcc-&gcc-suppress-libiberty-patch-version;.patch</userinput></screen></para> @@ -54,6 +54,10 @@ known ones):</para> 5 are still very much appropriate here. Be sure to refer back there should you have any doubts.</para> +<para>The test suite notes from <xref linkend="ch05-gcc-pass2"/> are still very +much appropriate here. Be sure to refer back there should you have any +doubts.</para> + <para>And install the package:</para> <para><screen><userinput>make install</userinput></screen></para> @@ -70,8 +74,9 @@ compiler. To satisfy those packages, create a symlink:</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> +we performed earlier in the chapter. Refer back to +<xref linkend="ch06-adjustingtoolchain"/> 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> |