Author: bdubbs
Date: 2007-10-05 13:21:39 -0600 (Fri, 05 Oct 2007)
New Revision: 8401
Modified:
branches/jh/BOOK/chapter01/changelog.xml
branches/jh/BOOK/chapter05/glibc.xml
branches/jh/BOOK/chapter06/glibc.xml
branches/jh/BOOK/chapter06/introduction.xml
branches/jh/BOOK/general.ent
Log:
Added -mtune to Glibc CFLAGS
Modified: branches/jh/BOOK/chapter01/changelog.xml
===================================================================
--- branches/jh/BOOK/chapter01/changelog.xml 2007-10-04 15:51:20 UTC (rev
8400)
+++ branches/jh/BOOK/chapter01/changelog.xml 2007-10-05 19:21:39 UTC (rev
8401)
@@ -37,6 +37,15 @@
-->
<listitem>
+ <para>2007-10-05</para>
+ <itemizedlist>
+ <listitem>
+ <para>[bdubbs] - Added -mtune to Glibc CFLAGS.</para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+
+ <listitem>
<para>2007-10-04</para>
<itemizedlist>
<listitem>
Modified: branches/jh/BOOK/chapter05/glibc.xml
===================================================================
--- branches/jh/BOOK/chapter05/glibc.xml 2007-10-04 15:51:20 UTC (rev
8400)
+++ branches/jh/BOOK/chapter05/glibc.xml 2007-10-05 19:21:39 UTC (rev
8401)
@@ -55,10 +55,13 @@
the flag is best placed inside the build variable <quote>CFLAGS</quote>.
Instead of overriding completely what Glibc's internal build system uses
for CFLAGS, append the new flag to the existing contents of CFLAGS by
- making use of the special file <filename>configparms</filename>:</para>
+ making use of the special file <filename>configparms</filename>. The
+ -mtune=native flag is also necessary to reset a reasonable value for -mtune
+ that is changed when setting -march.</para>
-<screen><userinput remap="configure">uname -m | grep -q i[4-7]86 &&
-echo "CFLAGS += -march=i486" > configparms</userinput></screen>
+<screen><userinput remap="configure">if [ uname -m | grep -q i[4-7]86 ]; do
+ echo "CFLAGS += -march=i486" > configparms
+done</userinput></screen>
<para>Next, prepare Glibc for compilation:</para>
Modified: branches/jh/BOOK/chapter06/glibc.xml
===================================================================
--- branches/jh/BOOK/chapter06/glibc.xml 2007-10-04 15:51:20 UTC (rev
8400)
+++ branches/jh/BOOK/chapter06/glibc.xml 2007-10-05 19:21:39 UTC (rev
8401)
@@ -104,10 +104,11 @@
<screen><userinput remap="pre">mkdir -v ../glibc-build
cd ../glibc-build</userinput></screen>
- <para>Again, add the needed compiler flag to CFLAGS for x86
machines:</para>
+ <para>Again, add the needed compiler flags to CFLAGS for x86
machines:</para>
-<screen><userinput remap="configure">uname -m | grep -q i[4-7]86 &&
-echo "CFLAGS += -march=i486" > configparms</userinput></screen>
+<screen><userinput remap="configure">if [ uname -m | grep -q i[4-7]86 ]; do
+ echo "CFLAGS += -march=i486" > configparms
+done</userinput></screen>
<para>Prepare Glibc for compilation:</para>
Modified: branches/jh/BOOK/chapter06/introduction.xml
===================================================================
--- branches/jh/BOOK/chapter06/introduction.xml 2007-10-04 15:51:20 UTC (rev
8400)
+++ branches/jh/BOOK/chapter06/introduction.xml 2007-10-05 19:21:39 UTC (rev
8401)
@@ -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
Modified: branches/jh/BOOK/general.ent
===================================================================
--- branches/jh/BOOK/general.ent 2007-10-04 15:51:20 UTC (rev 8400)
+++ branches/jh/BOOK/general.ent 2007-10-05 19:21:39 UTC (rev 8401)
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="ISO-8859-1"?>
-<!ENTITY version "SVN-JH-20071004">
-<!ENTITY releasedate "October 4, 2007">
+<!ENTITY version "SVN-JH-20071005">
+<!ENTITY releasedate "October 5, 2007">
<!ENTITY milestone "7.0">
<!ENTITY generic-version "development"> <!-- Use "development", "testing", or
"x.y[-pre{x}]" -->
--
http://linuxfromscratch.org/mailman/listinfo/lfs-book
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
