Author: jhuntwork
Date: 2007-03-02 16:23:14 -0700 (Fri, 02 Mar 2007)
New Revision: 7953
Modified:
trunk/BOOK/chapter01/changelog.xml
trunk/BOOK/chapter05/adjusting.xml
Log:
Warnings and important notices about a command that appear after instructions
to run it are evil.
Modified: trunk/BOOK/chapter01/changelog.xml
===================================================================
--- trunk/BOOK/chapter01/changelog.xml 2007-02-28 15:22:16 UTC (rev 7952)
+++ trunk/BOOK/chapter01/changelog.xml 2007-03-02 23:23:14 UTC (rev 7953)
@@ -37,6 +37,16 @@
-->
<listitem>
+ <para>2007-03-1</para>
+ <itemizedlist>
+ <listitem>
+ <para>[jhuntwork] - Minor grammatical changes. Move some warnings and
+ notices to appear before affected commands.</para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+
+ <listitem>
<para>2007-02-25</para>
<itemizedlist>
<listitem>
Modified: trunk/BOOK/chapter05/adjusting.xml
===================================================================
--- trunk/BOOK/chapter05/adjusting.xml 2007-02-28 15:22:16 UTC (rev 7952)
+++ trunk/BOOK/chapter05/adjusting.xml 2007-03-02 23:23:14 UTC (rev 7953)
@@ -32,25 +32,25 @@
<para>The next task is to point GCC to the new dynamic linker. This is done
by
dumping GCC's <quote>specs</quote> file to a location where GCC will look
for it
by default. A simple <command>sed</command> substitution then alters the
- dynamic linker that GCC will use:</para>
+ dynamic linker that GCC will use.</para>
-<!-- Ampersands are needed to allow copy and paste -->
-<screen><userinput>gcc -dumpspecs | sed '[EMAIL
PROTECTED]/lib/ld-linux.so.2@/tools&@g' \
- > `dirname $(gcc -print-libgcc-file-name)`/specs</userinput></screen>
+ <para>For the sake of accuracy, it is recommended to use a copy-and-paste
+ method when issuing the following command. Be sure to visually inspect the
+ specs file and verify that all occurrences of
<quote>/lib/ld-linux.so.2</quote>
+ have been replaced with <quote>/tools/lib/ld-linux.so.2</quote>.</para>
- <para>It is recommended that the above command be copy-and-pasted in order to
- ensure accuracy. Be sure to visually inspect the specs file in order to
- verify that all occurrences of <quote>/lib/ld-linux.so.2</quote> have been
- replaced with <quote>/tools/lib/ld-linux.so.2</quote>.</para>
-
<important>
<para>If working on a platform where the name of the dynamic linker is
something other than <filename
class="libraryfile">ld-linux.so.2</filename>,
replace <quote>ld-linux.so.2</quote> with the name of the platform's
- dynamic linker in the above commands. Refer back to <xref
+ dynamic linker in the following commands. Refer back to <xref
linkend="ch-tools-toolchaintechnotes" role=","/> if necessary.</para>
</important>
+<!-- Ampersands are needed to allow copy and paste -->
+<screen><userinput>gcc -dumpspecs | sed '[EMAIL
PROTECTED]/lib/ld-linux.so.2@/tools&@g' \
+ > `dirname $(gcc -print-libgcc-file-name)`/specs</userinput></screen>
+
<para>During the build process, GCC runs a script
(<command>fixincludes</command>) that scans the system for header files
that may need to be fixed (they might contain syntax errors, for example),
--
http://linuxfromscratch.org/mailman/listinfo/lfs-book
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
