aboutsummaryrefslogtreecommitdiffstats
path: root/chapter05/glibc.xml
diff options
context:
space:
mode:
Diffstat (limited to 'chapter05/glibc.xml')
-rw-r--r--chapter05/glibc.xml27
1 files changed, 3 insertions, 24 deletions
diff --git a/chapter05/glibc.xml b/chapter05/glibc.xml
index da354551c..e1561b096 100644
--- a/chapter05/glibc.xml
+++ b/chapter05/glibc.xml
@@ -43,27 +43,6 @@
<sect2 role="installation">
<title>Installation of Glibc</title>
- <para>First, create a symbolic link for LSB compliance. Additionally,
- for x86_64, create a compatibility symbolic link required for proper
- operation of the dynamic library loader:</para>
-
-<screen><userinput remap="pre">case $(uname -m) in
- i?86) ln -sfv ld-linux.so.2 $LFS/lib/ld-lsb.so.3
- ;;
- x86_64) ln -sfv ../lib/ld-linux-x86-64.so.2 $LFS/lib64
- ln -sfv ../lib/ld-linux-x86-64.so.2 $LFS/lib64/ld-lsb-x86-64.so.3
- ;;
-esac</userinput></screen>
-
- <note>
- <para>
- The above command is correct. The <command>ln</command> command has
- several syntactic versions, so be sure to check
- <command>info coreutils ln</command> and <filename>ln(1)</filename>
- before reporting what may appear to be an error.
- </para>
- </note>
-
<para>Some of the Glibc programs use the non-FHS-compliant
<filename class="directory">/var/db</filename> directory to store their
runtime data. Apply the following patch to make such programs store their
@@ -210,10 +189,10 @@ readelf -l a.out | grep ld-linux</userinput></screen>
<para>If everything is working correctly, there should be no errors,
and the output of the last command will be of the form:</para>
-<screen><computeroutput>[Requesting program interpreter: /lib64/ld-linux-x86-64.so.2]</computeroutput></screen>
+<screen><computeroutput>[Requesting program interpreter: /lib/ld-linux-aarch64.so.1]</computeroutput></screen>
- <para>Note that for 32-bit machines, the interpreter name will be
- <filename>/lib/ld-linux.so.2</filename>.</para>
+ <para>Note that for big-endian machines, the interpreter name will be
+ <filename>/lib/ld-linux-aarch64_be.so.1</filename>.</para>
<para>If the output is not as shown above, or there is no output at all,
then something is wrong. Investigate and retrace the steps to find out