diff options
| -rw-r--r-- | chapter01/changelog.xml | 3 | ||||
| -rw-r--r-- | chapter05/binutils-pass1.xml | 7 | ||||
| -rw-r--r-- | chapter05/binutils-pass2.xml | 7 | ||||
| -rw-r--r-- | chapter05/gcc-pass1.xml | 7 | ||||
| -rw-r--r-- | chapter05/gcc-pass2.xml | 7 | ||||
| -rw-r--r-- | chapter05/glibc.xml | 11 | ||||
| -rw-r--r-- | chapter06/binutils.xml | 7 | ||||
| -rw-r--r-- | chapter06/gcc.xml | 7 | ||||
| -rw-r--r-- | chapter06/glibc.xml | 7 | ||||
| -rw-r--r-- | chapter06/introduction.xml | 12 |
10 files changed, 10 insertions, 65 deletions
diff --git a/chapter01/changelog.xml b/chapter01/changelog.xml index e111f6db3..448e08c42 100644 --- a/chapter01/changelog.xml +++ b/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). 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—Tcl, Expect and DejaGNU—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> 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 |