Changeset 9829329 for chapter06


Ignore:
Timestamp:
11/06/2005 06:47:51 PM (19 years ago)
Author:
Matthew Burgess <matthew@…>
Branches:
10.0, 10.0-rc1, 10.1, 10.1-rc1, 11.0, 11.0-rc1, 11.0-rc2, 11.0-rc3, 11.1, 11.1-rc1, 11.2, 11.2-rc1, 11.3, 11.3-rc1, 12.0, 12.0-rc1, 12.1, 12.1-rc1, 6.3, 6.4, 6.5, 6.6, 6.7, 6.8, 7.0, 7.1, 7.2, 7.3, 7.4, 7.5, 7.5-systemd, 7.6, 7.6-systemd, 7.7, 7.7-systemd, 7.8, 7.8-systemd, 7.9, 7.9-systemd, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, arm, bdubbs/gcc13, ml-11.0, multilib, renodr/libudev-from-systemd, s6-init, trunk, xry111/arm64, xry111/arm64-12.0, xry111/clfs-ng, xry111/lfs-next, xry111/loongarch, xry111/loongarch-12.0, xry111/loongarch-12.1, xry111/mips64el, xry111/pip3, xry111/rust-wip-20221008, xry111/update-glibc
Children:
09043c0
Parents:
a5ebf89
Message:

Remove optimization related warnings from the toolchain packages

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

Location:
chapter06
Files:
4 edited

Legend:

Unmodified
Added
Removed
  • chapter06/binutils.xml

    ra5ebf89 r9829329  
    3232<title>Installation of Binutils</title>
    3333
    34 <para>This package is known to have issues when its default
    35 optimization flags (including the <parameter>-march</parameter> and
    36 <parameter>-mcpu</parameter> options) are changed. If any environment
    37 variables that override default optimizations have been defined, such
    38 as <envar>CFLAGS</envar> and <envar>CXXFLAGS</envar>,
    39 unset them when building Binutils.</para>
    40 
    4134<para>Verify that the PTYs are working properly inside the chroot
    4235environment. Check that everything is set up correctly by performing a
  • chapter06/gcc.xml

    ra5ebf89 r9829329  
    3232<title>Installation of GCC</title>
    3333
    34 <para>This package is known to have issues when its default
    35 optimization flags (including the <parameter>-march</parameter> and
    36 <parameter>-mcpu</parameter> options) are changed. If any environment
    37 variables that override default optimizations have been defined, such
    38 as <envar>CFLAGS</envar> and <envar>CXXFLAGS</envar>,
    39 unset them when building GCC.</para>
    40 
    4134<para>Apply a <command>sed</command> substitution that will suppress the
    4235installation of <filename class="libraryfile">libiberty.a</filename>. The
  • chapter06/glibc.xml

    ra5ebf89 r9829329  
    4242convert from/to Unicode, therefore libiconv is not required on an LFS
    4343system.</para></note>
    44 
    45 <para>This package is known to have issues when its default
    46 optimization flags (including the <parameter>-march</parameter> and
    47 <parameter>-mcpu</parameter> options) are changed. If any environment
    48 variables that override default optimizations have been defined, such
    49 as <envar>CFLAGS</envar> and <envar>CXXFLAGS</envar>,
    50 unset them when building Glibc.</para>
    5144
    5245<para>The Glibc build system is self-contained and will install
  • chapter06/introduction.xml

    ra5ebf89 r9829329  
    3232does compile when using optimization, there is the risk it may have
    3333been compiled incorrectly because of the complex interactions between
    34 the code and build tools.  The small potential gains achieved in using
    35 compiler optimizations are often outweighed by the risks. First-time
    36 builders of LFS are encouraged to build without custom optimizations.
    37 The subsequent system will still run very fast and be stable at the
    38 same time.</para>
     34the code and build tools.  Also note that the <option>-march</option>
     35and <option>-mtune</option> options may cause problems with the
     36toolchain packages (Binutils, GCC and Glibc).  The small potential
     37gains achieved in using compiler optimizations are often outweighed by
     38the risks. First-time builders of LFS are encouraged to build without
     39custom optimizations.  The subsequent system will still run very fast
     40and be stable at the same time.</para>
    3941
    4042<para>The order that packages are installed in this chapter needs to
Note: See TracChangeset for help on using the changeset viewer.