diff options
| author | Jeremy Huntwork <jhuntwork@linuxfromscratch.org> | 2008-12-03 22:46:04 +0000 |
|---|---|---|
| committer | Jeremy Huntwork <jhuntwork@linuxfromscratch.org> | 2008-12-03 22:46:04 +0000 |
| commit | 6e886330cf157dc71e6a0a1fca410d7005683167 (patch) | |
| tree | 0d8c4ae5a6429328469c512bb9f6661ad3886e19 /chapter06/introduction.xml | |
| parent | b0e1dc860c471d7047fc906001f3a336ef5f357c (diff) | |
Initial addition of support for x86_64
git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@8754 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
Diffstat (limited to 'chapter06/introduction.xml')
| -rw-r--r-- | chapter06/introduction.xml | 29 |
1 files changed, 15 insertions, 14 deletions
diff --git a/chapter06/introduction.xml b/chapter06/introduction.xml index 5268fb66a..291992fa4 100644 --- a/chapter06/introduction.xml +++ b/chapter06/introduction.xml @@ -23,20 +23,21 @@ followed by concise descriptions of each program and library the package installed.</para> - <para>If using compiler optimizations, please - review the optimization hint at <ulink url="&hints-root;optimization.txt"/>. - Compiler optimizations can make a program run slightly faster, but they may - also cause compilation difficulties and problems when running the program. - If a package 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. 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>If using compiler optimizations, please review the optimization hint at + <ulink url="&hints-root;optimization.txt"/>. Compiler optimizations can make + a program run slightly faster, but they may also cause compilation + difficulties and problems when running the program. If a package 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. Also note that + the <option>-march</option> and <option>-mtune</option> options using values + not specified in the book have not been tested. This 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 path |