aboutsummaryrefslogtreecommitdiffstats
path: root/chapter05/toolchaintechnotes.xml
diff options
context:
space:
mode:
authorJeremy Huntwork <jhuntwork@linuxfromscratch.org>2008-12-03 22:46:04 +0000
committerJeremy Huntwork <jhuntwork@linuxfromscratch.org>2008-12-03 22:46:04 +0000
commit6e886330cf157dc71e6a0a1fca410d7005683167 (patch)
tree0d8c4ae5a6429328469c512bb9f6661ad3886e19 /chapter05/toolchaintechnotes.xml
parentb0e1dc860c471d7047fc906001f3a336ef5f357c (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 'chapter05/toolchaintechnotes.xml')
-rw-r--r--chapter05/toolchaintechnotes.xml21
1 files changed, 9 insertions, 12 deletions
diff --git a/chapter05/toolchaintechnotes.xml b/chapter05/toolchaintechnotes.xml
index cc1f7242e..f6adefb61 100644
--- a/chapter05/toolchaintechnotes.xml
+++ b/chapter05/toolchaintechnotes.xml
@@ -27,24 +27,21 @@
<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>i686-pc-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
referred to as the dynamic loader (not to be confused with the standard
linker <command>ld</command> that is part of Binutils). The dynamic linker
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.so.2</filename>.
- On platforms that are less prevalent, the name might be <filename
- class="libraryfile">ld.so.1</filename>, and newer 64 bit platforms might
- be named something else entirely. 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>
and noting the output. The authoritative reference covering all platforms