Remove optimization related warnings from the toolchain packages

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

chapter01/changelog.xml

@@ -116,6 +116,9 @@ First a summary, then a detailed log.</para>
 </itemizedlist>
 </listitem>
 
+<listitem><para>November 6, 2005 [matt]: Remove the optimization related
+warnings from the toolchain packages (bug 1650).</para></listitem>
+
 <listitem><para>November 6, 2005 [matt]: Install Vim's documentation to
 <filename class="directory">/usr/share/doc/vim-&vim-version;</filename> instead
 of <filename class="directory">/usr/share/vim/vim64/doc</filename> (bug 1610).

chapter05/binutils-pass1.xml

@@ -34,13 +34,6 @@ because both Glibc and GCC perform various tests on the available
 linker and assembler to determine which of their own features to
 enable.</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
-variables that override default optimizations have been defined, such
-as <envar>CFLAGS</envar> and <envar>CXXFLAGS</envar>,
-unset them when building Binutils.</para>
-
 <para>The Binutils documentation recommends building Binutils outside of the
 source directory in a dedicated build directory:</para>
 

chapter05/binutils-pass2.xml

@@ -33,13 +33,6 @@
 <sect2 role="installation">
 <title>Re-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>Create a separate build directory again:</para>
 
 <screen><userinput>mkdir -v ../binutils-build

chapter05/gcc-pass1.xml

@@ -29,13 +29,6 @@
 <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>The GCC documentation recommends building GCC outside of the
 source directory in a dedicated build directory:</para>
 

chapter05/gcc-pass2.xml

@@ -28,13 +28,6 @@
 <sect2 role="installation">
 <title>Re-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>The tools required to test GCC and Binutils&mdash;Tcl, Expect
 and DejaGNU&mdash;are installed now. GCC and Binutils can now be
 rebuilt, linking them against the new Glibc and testing them properly

chapter05/glibc.xml

@@ -29,17 +29,6 @@
 <sect2 role="installation">
 <title>Installation of Glibc</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 Glibc.</para>
-
-<para>It should be noted that compiling Glibc in any way other than
-the method suggested in this book puts the stability of the system at
-risk.</para>
-
 <para>The Glibc documentation recommends building Glibc outside of the source
 directory in a dedicated build directory:</para>
 

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>

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

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

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