Changeset da2f9fe for chapter05

Timestamp:

08/07/2007 08:24:04 PM (17 years ago)

Author:

Jeremy Huntwork <jhuntwork@…>

Children:

71f6077

Parents:

400af5a8

Message:

• Upgraded to HJL Binutils-2.17.50.0.18
• Initial update of commands to work with both x86 and x86_64

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

Location:

chapter05

Files:

• adjusting.xml (modified) (2 diffs)
• toolchaintechnotes.xml (modified) (3 diffs)

chapter05/adjusting.xml

@@ -37 +37 @@
   <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>/lib64/ld-linux-x86-64.so.2</quote>
-  have been replaced with <quote>/tools/lib64/ld-linux-x86-64.so.2</quote>:</para>
+  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>
 
   <important>
     <para>If working on a platform where the name of the dynamic linker is
-    something other than <filename class="libraryfile">ld-linux-x86-64.so.2</filename>,
-    replace <quote>ld-linux-x86-64.so.2</quote> with the name of the platform's
+    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 following commands. Refer to <xref
-    linkend="ch-tools-toolchaintechnotes" role=","/> if necessary.</para>
+    linkend="ch-tools-toolchaintechnotes" role=","/> if necessary. Additionally,
+    note that on 64-bit machines the linker may actually be expected in the
+    <filename class="directory">/lib64</filename> directory.</para>
   </important>
 
 <!-- Ampersands are needed to allow copy and paste -->
-<screen><userinput>gcc -dumpspecs | sed 's@/lib64/ld-linux-x86-64.so.2@/tools&amp;@g' \
-  > `dirname $(gcc -print-libgcc-file-name)`/specs</userinput></screen>
+<screen><userinput>gcc -dumpspecs | sed 's@/lib\(64\)\?/ld@/tools&amp;@g' \
+  &gt; `dirname $(gcc -print-libgcc-file-name)`/specs</userinput></screen>
 
   <para>During the build process, GCC runs a script
@@ -85 +87 @@
 
 <screen><computeroutput>[Requesting program interpreter:
-    /tools/lib64/ld-linux-x86-64.so.2]</computeroutput></screen>
+    /tools/lib/ld-linux.so.2]</computeroutput></screen>
 
-    <para>Note that <filename class="directory">/tools/lib</filename>
+    <para>Note that <filename class="directory">/tools/lib</filename>, or
+    <filename class="directory">/tools/lib64</filename> for 64-bit machines
     appears as the prefix of the dynamic linker.</para>
 

chapter05/toolchaintechnotes.xml

@@ -28 +28 @@
   <important>
     <para>Before continuing, be aware of the name of the working platform,
-    often referred to as the target triplet. Many times, the target
-    triplet will probably be <emphasis>x86_64-unknown-linux-gnu</emphasis>. A
-    simple way to determine the name of the target triplet is to run the
-    <command>config.guess</command> script that comes with the source for
-    many packages. Unpack the Binutils sources and run the script:
-    <userinput>./config.guess</userinput> and note the output.</para>
+    often referred to as the target triplet. A simple way to determine the
+    name of the target triplet is to run the <command>config.guess</command>
+    script that comes with the source for many packages. Unpack the Binutils
+    sources and run the script: <userinput>./config.guess</userinput> and note
+    the output. For example, for a modern 32-bit Intel processor the
+    output will likely be <emphasis>i686-pc-linux-gnu</emphasis>.</para>
 
     <para>Also be aware of the name of the platform's dynamic linker, often
@@ -40 +40 @@
     provided by Glibc finds and loads the shared libraries needed by a program,
     prepares the program to run, and then runs it. The name of the dynamic
-    linker will usually be <filename class="libraryfile">ld-linux-x86-64.so.2</filename>.
-    The name of the platform's dynamic linker can be determined by looking in the
-    <filename class="directory">/lib</filename>
-    directory on the host system. A sure-fire way to determine the name is to
+    linker for a 32-bit Intel machine will be
+    <filename class="libraryfile">ld-linux.so.2</filename>.
+    A sure-fire way to determine the name of the dynamic linker is to
     inspect a random binary from the host system by running:
     <userinput>readelf -l &lt;name of binary&gt; | grep interpreter</userinput>
@@ -97 +96 @@
 
 <screen><computeroutput>checking what assembler to use...
-        /tools/x86_64-unknown-linux-gnu/bin/as
-checking what linker to use... /tools/x86_64-unknown-linux-gnu/bin/ld</computeroutput></screen>
+        /tools/i686-pc-linux-gnu/bin/as
+checking what linker to use... /tools/i686-pc-linux-gnu/bin/ld</computeroutput></screen>
 
   <para>This is important for the reasons mentioned above. It also demonstrates