Ignore:
Timestamp:
12/03/2008 10:46:04 PM (15 years ago)
Author:
Jeremy Huntwork <jhuntwork@…>
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.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:
4e82d47
Parents:
b0e1dc8
Message:

Initial addition of support for x86_64

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

File:
1 edited

Legend:

Unmodified
Added
Removed

  • chapter06/introduction.xml

    rb0e1dc8 r6e88633  
    2424  installed.</para>
    2525
    26   <para>If using compiler optimizations, please
    27   review the optimization hint at <ulink url="&hints-root;optimization.txt"/>.
    28   Compiler optimizations can make a program run slightly faster, but they may
    29   also cause compilation difficulties and problems when running the program.
    30   If a package refuses to compile when using optimization, try to compile it
    31   without optimization and see if that fixes the problem. Even if the package
    32   does compile when using optimization, there is the risk it may have been
    33   compiled incorrectly because of the complex interactions between the code
    34   and build tools.  Also note that the <option>-march</option> and
    35   <option>-mtune</option> options may cause problems with the toolchain packages
    36   (Binutils, GCC and Glibc).  The small potential gains achieved in using
    37   compiler optimizations are often outweighed by the risks. First-time builders
    38   of LFS are encouraged to build without custom optimizations. The subsequent
    39   system will still run very fast and be stable at the same time.</para>
     26  <para>If using compiler optimizations, please review the optimization hint at
     27  <ulink url="&hints-root;optimization.txt"/>.  Compiler optimizations can make
     28  a program run slightly faster, but they may also cause compilation
     29  difficulties and problems when running the program.  If a package refuses to
     30  compile when using optimization, try to compile it without optimization and
     31  see if that fixes the problem. Even if the package does compile when using
     32  optimization, there is the risk it may have been compiled incorrectly because
     33  of the complex interactions between the code and build tools.  Also note that
     34  the <option>-march</option> and <option>-mtune</option> options using values
     35  not specified in the book have not been tested. This may cause problems with
     36  the toolchain packages (Binutils, GCC and Glibc).  The small potential gains
     37  achieved in using compiler optimizations are often outweighed by the risks.
     38  First-time builders of LFS are encouraged to build without custom
     39  optimizations. The subsequent system will still run very fast and be stable
     40  at the same time.</para>
    4041
    4142  <para>The order that packages are installed in this chapter needs to be
Note: See TracChangeset for help on using the changeset viewer.