Browse Source

Removed references to separate gcc tarballs. (Merged from trunk r5919)

git-svn-id: http://svn.linuxfromscratch.org/LFS/branches/6.1/BOOK@5937 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
Archaic 20 years ago
parent
commit
5a553316f3
5 changed files with 6 additions and 17 deletions
  1. 3 0
      chapter01/changelog.xml
  2. 1 6
      chapter05/gcc-pass1.xml
  3. 0 6
      chapter05/gcc-pass2.xml
  4. 0 3
      chapter06/gcc.xml
  5. 2 2
      general.ent

+ 3 - 0
chapter01/changelog.xml

@@ -84,6 +84,9 @@ First a summary, then a detailed log.</para>
 </itemizedlist>
 </listitem>
 
+<listitem><para>June 14th, 2005 [archaic]: Removed references to separate gcc
+tarballs (gcc-core, gcc-g++, etc.)</para></listitem>
+
 <listitem><para>June 12th, 2005 [matt]: Upgraded to linux-2.6.11.12.</para></listitem>
 
 <listitem><para>June 8th, 2005 [archaic]: Removed suggestion on where to move

+ 1 - 6
chapter05/gcc-pass1.xml

@@ -27,9 +27,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
@@ -74,9 +71,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>
 

+ 0 - 6
chapter05/gcc-pass2.xml

@@ -56,12 +56,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-&gcc-version;-no_fixincludes-1.patch

+ 0 - 3
chapter06/gcc.xml

@@ -36,9 +36,6 @@ variables that override default optimizations have been defined, such
 as <envar>CFLAGS</envar> and <envar>CXXFLAGS</envar>,
 unset them when building GCC.</para>
 
-<para>Unpack both the gcc-core and the gcc-g++ tarballs&mdash;they will unpack
-into the same directory. Likewise, extract the gcc-testsuite tarball.</para>
-
 <para>Apply only the No-Fixincludes patch (not the Specs patch) also
 used in the previous chapter:</para>
 

+ 2 - 2
general.ent

@@ -1,6 +1,6 @@
 <?xml version="1.0" encoding="ISO-8859-1"?>
-<!ENTITY version "TESTING-20050612">
-<!ENTITY releasedate "June 12, 2005">
+<!ENTITY version "TESTING-20050614">
+<!ENTITY releasedate "June 14, 2005">
 <!ENTITY milestone "6.1">
 
 <!ENTITY lfs-root "http://www.linuxfromscratch.org/">