diff options
| author | Bruce Dubbs <bdubbs@linuxfromscratch.org> | 2016-01-31 16:19:36 +0000 |
|---|---|---|
| committer | Bruce Dubbs <bdubbs@linuxfromscratch.org> | 2016-01-31 16:19:36 +0000 |
| commit | e1c388239f1a6c01668a31a737333741ae913a00 (patch) | |
| tree | 796bc13b30b0f53a9549cea36848a906f03e3794 /chapter05/toolchaintechnotes.xml | |
| parent | f1dd5475c93b2464957212d8e81b94d5b5af9630 (diff) | |
Fix a leftover reference to glibc-build
Text updates.
git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@10995 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
Diffstat (limited to 'chapter05/toolchaintechnotes.xml')
| -rw-r--r-- | chapter05/toolchaintechnotes.xml | 22 |
1 files changed, 12 insertions, 10 deletions
diff --git a/chapter05/toolchaintechnotes.xml b/chapter05/toolchaintechnotes.xml index 36c07bad3..252ea5262 100644 --- a/chapter05/toolchaintechnotes.xml +++ b/chapter05/toolchaintechnotes.xml @@ -30,22 +30,24 @@ 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> + the output. For example, for a 32-bit Intel processor the + output will be <emphasis>i686-pc-linux-gnu</emphasis>. On a 64-bit + system it will be <emphasis>x86_64-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 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 <name of binary> | grep interpreter</userinput> - and noting the output. The authoritative reference covering all platforms - is in the <filename>shlib-versions</filename> file in the root of the Glibc - source tree.</para> + linker for a 32-bit Intel machine will be <filename + class="libraryfile">ld-linux.so.2</filename> (<filename + class="libraryfile">ld-linux-x86-64.so.2</filename> for 64-bit systems). 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 + <name of binary> | grep interpreter</userinput> and noting the + output. The authoritative reference covering all platforms is in the + <filename>shlib-versions</filename> file in the root of the Glibc source + tree.</para> </note> <para>Some key technical points of how the <xref |