Remove optimization related warnings from the toolchain packages

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

5 files changed, 0 insertions, 39 deletions

diff --git a/chapter05/binutils-pass1.xml b/chapter05/binutils-pass1.xml
index 2b8d9312a..0849dd4cb 100644
--- a/chapter05/binutils-pass1.xml
+++ b/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>
 
diff --git a/chapter05/binutils-pass2.xml b/chapter05/binutils-pass2.xml
index 1d2368fce..2e64c3ed5 100644
--- a/chapter05/binutils-pass2.xml
+++ b/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
diff --git a/chapter05/gcc-pass1.xml b/chapter05/gcc-pass1.xml
index 758164c27..10f801167 100644
--- a/chapter05/gcc-pass1.xml
+++ b/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>
 
diff --git a/chapter05/gcc-pass2.xml b/chapter05/gcc-pass2.xml
index 998ef3659..f62886115 100644
--- a/chapter05/gcc-pass2.xml
+++ b/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
diff --git a/chapter05/glibc.xml b/chapter05/glibc.xml
index 7c99a9b1a..d40b93297 100644
--- a/chapter05/glibc.xml
+++ b/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>