Author: bdubbs
Date: 2009-05-16 21:20:56 -0600 (Sat, 16 May 2009)
New Revision: 8883

Modified:
   trunk/BOOK/chapter01/changelog.xml
   trunk/BOOK/chapter05/gcc-pass2.xml
   trunk/BOOK/chapter06/gcc.xml
Log:
Correct bootstrap explanation in gcc sections.  Thanks to Chris Staub.

Modified: trunk/BOOK/chapter01/changelog.xml
===================================================================
--- trunk/BOOK/chapter01/changelog.xml  2009-05-17 02:57:28 UTC (rev 8882)
+++ trunk/BOOK/chapter01/changelog.xml  2009-05-17 03:20:56 UTC (rev 8883)
@@ -41,6 +41,12 @@
       <para>2009-05-16</para>
       <itemizedlist>
         <listitem>
+          <para>[bdubbs] - Update gcc instruction explanations.
+          Thanks to Chris Staub for the patch.
+          Fixes
+          <ulink url="&lfs-ticket-root;2363">#2363</ulink>.</para>
+        </listitem>
+        <listitem>
           <para>[bdubbs] - Add an explanation about using the barrier
           option in fstab.
           Fixes

Modified: trunk/BOOK/chapter05/gcc-pass2.xml
===================================================================
--- trunk/BOOK/chapter05/gcc-pass2.xml  2009-05-17 02:57:28 UTC (rev 8882)
+++ trunk/BOOK/chapter05/gcc-pass2.xml  2009-05-17 03:20:56 UTC (rev 8883)
@@ -66,10 +66,11 @@
 <screen><userinput remap="pre">cp -v gcc/Makefile.in{,.orig}
 sed 's...@\./fixinc\...@-c true@' gcc/Makefile.in.orig &gt; 
gcc/Makefile.in</userinput></screen>
 
-    <para>Non-bootstrap builds omit the <option>-fomit-frame-pointer</option>
-    build flag by default, and the goal should be to produce a compiler that is
-    exactly the same as if it were bootstrapped. Apply the following
-    <command>sed</command> command to force the build to use the flag:</para>
+    <para>For x86 machines, a bootstrap build of GCC uses the
+    <option>-fomit-frame-pointer</option> compiler flag.  Non-bootstrap builds
+    omit this flag by default, and the goal should be to produce a compiler
+    that is exactly the same as if it were bootstrapped.  Apply the following
+    <command>sed</command> command to force the build to use the flag:</para> 
 
 <screen><userinput remap="pre">cp -v gcc/Makefile.in{,.tmp}
 sed 's/^XCFLAGS =$/&amp; -fomit-frame-pointer/' gcc/Makefile.in.tmp \
@@ -209,9 +210,14 @@
       <varlistentry>
         <term><parameter>--disable-bootstrap</parameter></term>
         <listitem>
-          <para>Bootstrapping the compiler is now the default for GCC. However,
-          our build method should provide us with a solid compiler without the
-          need to bootstrap each time.</para>
+          <para>For native builds of GCC, the default is to a "bootstrap" 
build.
+          This does not just compile GCC, but compiles it several times. It
+          uses the programs compiled in a first round to compile itself a
+          second time, and then again a third time.  The second and third
+          iterations are compared to make sure it can reproduce itself
+          flawlessly. This also implies that it was compiled correctly.
+          However, the LFS build method should provide a solid compiler
+          without the need to bootstrap each time.</para> 
         </listitem>
       </varlistentry>
 

Modified: trunk/BOOK/chapter06/gcc.xml
===================================================================
--- trunk/BOOK/chapter06/gcc.xml        2009-05-17 02:57:28 UTC (rev 8882)
+++ trunk/BOOK/chapter06/gcc.xml        2009-05-17 03:20:56 UTC (rev 8883)
@@ -48,12 +48,10 @@
 
 <screen><userinput remap="pre">sed -i 's/install_to_$(INSTALL_DEST) //' 
libiberty/Makefile.in</userinput></screen>
 
-    <para>For x86 machines, the bootstrap build performed in
-    <xref linkend="ch-tools-gcc-pass2"/>
-    built GCC with the <option>-fomit-frame-pointer</option> compiler flag.
-    Non-bootstrap builds omit this flag by default, so apply the following
-    <command>sed</command> to use it in order to ensure consistent compiler
-    builds:</para>
+    <para>As in <xref linkend="ch-tools-gcc-pass2"/>, apply the following
+    <command>sed</command> to force the build to use the
+    <option>-fomit-frame-pointer</option> compiler flag in order to ensure
+    consistent compiler builds:</para> 
 
 <screen><userinput remap="pre">case `uname -m` in
   i?86) sed -i 's/^XCFLAGS =$/&amp; -fomit-frame-pointer/' \

-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-book
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

Reply via email to