Remove optimization related warnings from the toolchain packages

git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@7131 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

4 files changed, 7 insertions, 26 deletions

diff --git a/chapter06/binutils.xml b/chapter06/binutils.xml
index b9113ff57..cd1055298 100644
--- a/chapter06/binutils.xml
+++ b/chapter06/binutils.xml
@@ -31,13 +31,6 @@ Glibc, Grep, M4, Make, Perl, Sed, and Texinfo</seg></seglistitem>
 <sect2 role="installation">
 <title>Installation of Binutils</title>
 
-<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
-variables that override default optimizations have been defined, such
-as <envar>CFLAGS</envar> and <envar>CXXFLAGS</envar>,
-unset them when building Binutils.</para>
-
 <para>Verify that the PTYs are working properly inside the chroot
 environment. Check that everything is set up correctly by performing a
 simple test:</para>
diff --git a/chapter06/gcc.xml b/chapter06/gcc.xml
index 469162b21..44ecc2907 100644
--- a/chapter06/gcc.xml
+++ b/chapter06/gcc.xml
@@ -31,13 +31,6 @@ Gawk, Gettext, Glibc, Grep, Make, Perl, Sed, and Texinfo</seg></seglistitem>
 <sect2 role="installation">
 <title>Installation of GCC</title>
 
-<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
-variables that override default optimizations have been defined, such
-as <envar>CFLAGS</envar> and <envar>CXXFLAGS</envar>,
-unset them when building GCC.</para>
-
 <para>Apply a <command>sed</command> substitution that will suppress the
 installation of <filename class="libraryfile">libiberty.a</filename>. The
 version of <filename class="libraryfile">libiberty.a</filename> provided by
diff --git a/chapter06/glibc.xml b/chapter06/glibc.xml
index 8e5abee70..1032c7862 100644
--- a/chapter06/glibc.xml
+++ b/chapter06/glibc.xml
@@ -42,13 +42,6 @@ which don't have one, or whose implementation cannot convert from/to Unicode.
 convert from/to Unicode, therefore libiconv is not required on an LFS
 system.</para></note>
 
-<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
-variables that override default optimizations have been defined, such
-as <envar>CFLAGS</envar> and <envar>CXXFLAGS</envar>,
-unset them when building Glibc.</para>
-
 <para>The Glibc build system is self-contained and will install
 perfectly, even though the compiler specs file and linker are still
 pointing at <filename class="directory">/tools</filename>. The specs
diff --git a/chapter06/introduction.xml b/chapter06/introduction.xml
index 12c4a01f6..51845cd85 100644
--- a/chapter06/introduction.xml
+++ b/chapter06/introduction.xml
@@ -31,11 +31,13 @@ refuses to compile when using optimization, try to compile it without
 optimization and see if that fixes the problem. Even if the package
 does compile when using optimization, there is the risk it may have
 been compiled incorrectly because of the complex interactions between
-the code and build tools.  The small potential gains achieved in using
-compiler optimizations are often outweighed by the risks. First-time
-builders of LFS are encouraged to build without custom optimizations.
-The subsequent system will still run very fast and be stable at the
-same time.</para>
+the code and build tools.  Also note that the <option>-march</option>
+and <option>-mtune</option> options may cause problems with the
+toolchain packages (Binutils, GCC and Glibc).  The small potential
+gains achieved in using compiler optimizations are often outweighed by
+the risks. First-time builders of LFS are encouraged to build without
+custom optimizations.  The subsequent system will still run very fast
+and be stable at the same time.</para>
 
 <para>The order that packages are installed in this chapter needs to
 be strictly followed to ensure that no program accidentally acquires a