Changeset 531b5e5 for final-system/common

Timestamp:

Feb 21, 2006, 12:47:43 AM (19 years ago)

Author:

Jim Gifford <clfs@…>

Children:

6301b6a

Parents:

af98896

Message:

r649@server (orig r647): manuel | 2005-11-07 12:51:45 -0800
Remove the optimization related warnings from the toolchain packages.

Location:

final-system/common

Files:

• binutils.xml (modified) (1 diff)
• gcc.xml (modified) (1 diff)
• glibc.xml (modified) (3 diffs)
• introduction.xml (modified) (1 diff)

final-system/common/binutils.xml

@@ -46 +46 @@
   <sect2 role="installation">
     <title>Installation of Binutils</title>
-
-    <para os="a">This package is known to have issues when its default
-    optimization flags (including the <option>-march</option> and
-    <option>-mcpu</option> 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 os="b">Verify that the PTYs are working properly inside the build

final-system/common/gcc.xml

@@ -47 +47 @@
     <title>Installation of GCC</title>
 
-    <para os="a">This package is known to have issues when its default
-    optimization flags (including the <option>-march</option> and
-    <option>-mcpu</option> 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 os="d">Apply a <command>sed</command> substitution that will suppress the
     installation of <filename class="libraryfile">libiberty.a</filename>. The

final-system/common/glibc.xml

@@ -60 +60 @@
     </note>
 
-    <para os="a">This package is known to behave badly when you change its default
-    optimization flags (including the <option>-march</option> and
-    <option>-mcpu</option> options). Therefore, if you have defined any
-    environment variables that override default optimizations, such as CFLAGS
-    and CXXFLAGS, we recommend un-setting them when building Glibc.</para>
-
     <para os="b">The Glibc build system is self-contained and will install
     perfectly, even though the compiler specs file and linker are still
@@ -77 +71 @@
 
 <screen os="d"><userinput>patch -Np1 -i ../&glibc-localedef_segfault-patch;</userinput></screen>
- 
+
     <para os="e">The Glibc documentation recommends building Glibc outside of the
     source directory in a dedicated build directory:</para>
@@ -128 +122 @@
       <listitem>
         <para>The <emphasis>math</emphasis> tests, at least on i686, fail in
-        the <emphasis>test-double</emphasis> and <emphasis>test-idouble</emphasis>
-        tests with gcc-&gcc-version;, the <command>grep</command> command will
-        also report an expected (ignored) failure in <emphasis>posix/annexc
-        </emphasis>. These two failures in the math tests appear to be harmless.
-        The math tests may also fail    
+  the <emphasis>test-double</emphasis> and <emphasis>test-idouble</emphasis>
+  tests with gcc-&gcc-version;, the <command>grep</command> command will
+  also report an expected (ignored) failure in <emphasis>posix/annexc
+  </emphasis>. These two failures in the math tests appear to be harmless.
+  The math tests may also fail
         on systems where the CPU is not a relatively new genuine Intel or
         authentic AMD. Certain optimization settings are also known to be a

final-system/common/introduction.xml

@@ -31 +31 @@
   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
+  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