From c18558ce3373d6ba536c760b42cccc97f16c0e23 Mon Sep 17 00:00:00 2001 From: Xi Ruoyao Date: Wed, 24 Aug 2022 23:29:04 +0800 Subject: [PATCH] arm64: remove ld.so symlink creation It's not need for ARM64! --- chapter05/glibc.xml | 21 --------------------- 1 file changed, 21 deletions(-) diff --git a/chapter05/glibc.xml b/chapter05/glibc.xml index 103fa42c8..c07db65e9 100644 --- a/chapter05/glibc.xml +++ b/chapter05/glibc.xml @@ -43,27 +43,6 @@ Installation of Glibc - 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: - -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 - - - - The above command is correct. The ln command has - a few syntactic versions, so be sure to check - info coreutils ln and ln(1) - before reporting what you may think is an error. - - - Some of the Glibc programs use the non-FHS compliant /var/db directory to store their runtime data. Apply the following patch to make such programs store their