diff --git a/chapter01/changelog.xml b/chapter01/changelog.xml
index fa9d182b9..4e52f9571 100644
--- a/chapter01/changelog.xml
+++ b/chapter01/changelog.xml
@@ -88,6 +88,9 @@ First a summary, then a detailed log.
+June 14th, 2005 [archaic]: Removed references to separate gcc
+tarballs (gcc-core, gcc-g++, etc.)
+
June 14th, 2005 [archaic]: Updated all build sizes.
June 12th, 2005 [matt]: Upgraded to linux-2.6.11.12.
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 @@
Installation of GCC
-Unpack only the gcc-core tarball because neither the C++
-compiler nor the test suite will be needed here.
-
This package is known to have issues when its default
optimization flags (including the -march and
-mcpu options) are changed. If any environment
@@ -76,9 +73,7 @@ results.
--enable-languages=c
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.
+
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 for more
information on how to get PTYs working.
-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 gcc-&gcc-version;/ subdirectory.
-
First correct a known problem and make an essential adjustment:
patch -Np1 -i ../&gcc-no_fixincludes-patch;
diff --git a/chapter06/gcc.xml b/chapter06/gcc.xml
index 150ce623a..05e5f50ba 100644
--- a/chapter06/gcc.xml
+++ b/chapter06/gcc.xml
@@ -38,9 +38,6 @@ variables that override default optimizations have been defined, such
as CFLAGS and CXXFLAGS,
unset them when building GCC.
-Unpack both the gcc-core and the gcc-g++ tarballs—they will unpack
-into the same directory. Likewise, extract the gcc-testsuite tarball.
-
Apply only the No-Fixincludes patch (not the Specs patch) also
used in the previous chapter: