diff options
author | Archaic <archaic@linuxfromscratch.org> | 2005-06-14 16:15:58 +0000 |
---|---|---|
committer | Archaic <archaic@linuxfromscratch.org> | 2005-06-14 16:15:58 +0000 |
commit | dc0e9159c454159eb251bc99482da0d69d9d7762 (patch) | |
tree | 6c158c24ae2044c6d6f8b424eb08250ca0f13ab8 /chapter05 | |
parent | a4ee3d2cefe04174d9cb55f55cf7eda8a549ffc3 (diff) |
Removed references to separate gcc tarballs.
git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@5919 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
Diffstat (limited to 'chapter05')
-rw-r--r-- | chapter05/gcc-pass1.xml | 7 | ||||
-rw-r--r-- | chapter05/gcc-pass2.xml | 6 |
2 files changed, 1 insertions, 12 deletions
diff --git a/chapter05/gcc-pass1.xml b/chapter05/gcc-pass1.xml index a02f34120..a960d1ae1 100644 --- a/chapter05/gcc-pass1.xml +++ b/chapter05/gcc-pass1.xml @@ -29,9 +29,6 @@ <sect2 role="installation"> <title>Installation of GCC</title> -<para>Unpack only the gcc-core tarball because neither the C++ -compiler nor the test suite will be needed here.</para> - <para>This package is known to have issues when its default optimization flags (including the <parameter>-march</parameter> and <parameter>-mcpu</parameter> options) are changed. If any environment @@ -76,9 +73,7 @@ results.</para></listitem> <varlistentry> <term><parameter>--enable-languages=c</parameter></term> <listitem><para>This option ensures that only the C compiler is built. -This option is only needed when you have downloaded and unpacked the -full GCC tarball, as opposed to just the gcc-core -tarball.</para></listitem> +</para></listitem> </varlistentry> </variablelist> diff --git a/chapter05/gcc-pass2.xml b/chapter05/gcc-pass2.xml index 205f5be89..c25431601 100644 --- a/chapter05/gcc-pass2.xml +++ b/chapter05/gcc-pass2.xml @@ -58,12 +58,6 @@ test suites for GCC and Binutils until this issue is resolved. Please consult the LFS Wiki at <ulink url="&wiki-root;"/> for more information on how to get PTYs working.</para> -<para>Because the C and the C++ compilers will be built, unpack both -the core and the g++ tarballs (as well as test suite, if you want to -run the tests). By unpacking them in the working directory, they will -all unfold into a single <filename -class="directory">gcc-&gcc-version;/</filename> subdirectory.</para> - <para>First correct a known problem and make an essential adjustment:</para> <screen><userinput>patch -Np1 -i ../&gcc-no_fixincludes-patch; |