Testing by trying to execute /sbin/ldconfig within the aarch64 Debian bullseye chroot on 20.04 amd64 host for all installed kernels is working, including 5.12.0, the version booted to by default !
That is: 5.4.0-73-lowlatency 5.8.0-41-lowlatency 5.10.2 5.11.0+ 5.12.0-elloe+
This is extremely difficult to understand since I only got involved in reproducing and testing this on my PC when my colleague hit this issue (recall his PC is on v5.10.0).
Now, using qemu-debootstrap to build a new Debian bullseye also works (remembering to set ownership on the directory to root first!).
$ uname -a
Linux elloe000 5.12.0-elloe+ #31 SMP PREEMPT Sat May 1 10:46:45 BST 2021 x86_64 x86_64 x86_64 GNU/Linux
$ sudo mkdir bullseye2-arm64
$ sudo qemu-debootstrap --arch=arm64 bullseye bullseye2-arm64 http://ftp.debian.o
rg/debian
I: Running command: debootstrap --arch arm64 --foreign bullseye bullseye2-arm64 http://ftp.debian.org/debian
I: Retrieving InRelease
I: Checking Release signature
I: Valid Release signature (key id 0146DC6D4A0B2914BDED34DB648ACFD622F3D138)
I: Retrieving Packages
I: Validating Packages
I: Resolving dependencies of required packages...
I: Resolving dependencies of base packages...
I: Checking component main on http://ftp.debian.org/debian...
...
I: Running command: chroot bullseye2-arm64 /debootstrap/debootstrap --second-stage
I: Installing core packages...
...
I: Unpacking the base system...
...
I: Configuring libc-bin...
I: Base system installed successfully.
$ sudo chroot bullseye2-arm64/ /sbin/ldconfig -v
/sbin/ldconfig: Can't stat /usr/local/lib/aarch64-linux-gnu: No such file or directory
/sbin/ldconfig: Path `/usr/lib/aarch64-linux-gnu' given more than once
/sbin/ldconfig: Path `/lib/aarch64-linux-gnu' given more than once
/sbin/ldconfig: Path `/usr/lib/aarch64-linux-gnu' given more than once
/sbin/ldconfig: Path `/usr/lib' given more than once
/lib/aarch64-linux-gnu: libSegFault.so -> libSegFault.so
...
/sbin/ldconfig: /lib/aarch64-linux-gnu/ld-2.31.so is the dynamic linker, ignoring
Testing by trying to execute /sbin/ldconfig within the aarch64 Debian bullseye chroot on 20.04 amd64 host for all installed kernels is working, including 5.12.0, the version booted to by default !
That is: 5.4.0-73-lowlatency 5.8.0-41-lowlatency 5.10.2 5.11.0+ 5.12.0-elloe+
This is extremely difficult to understand since I only got involved in reproducing and testing this on my PC when my colleague hit this issue (recall his PC is on v5.10.0).
Now, using qemu-debootstrap to build a new Debian bullseye also works (remembering to set ownership on the directory to root first!).
$ uname -a
Linux elloe000 5.12.0-elloe+ #31 SMP PREEMPT Sat May 1 10:46:45 BST 2021 x86_64 x86_64 x86_64 GNU/Linux
$ sudo mkdir bullseye2-arm64
$ sudo qemu-debootstrap --arch=arm64 bullseye bullseye2-arm64 http:// ftp.debian. o ftp.debian. org/debian 4BDED34DB648ACF D622F3D138) ftp.debian. org/debian... debootstrap --second-stage
rg/debian
I: Running command: debootstrap --arch arm64 --foreign bullseye bullseye2-arm64 http://
I: Retrieving InRelease
I: Checking Release signature
I: Valid Release signature (key id 0146DC6D4A0B291
I: Retrieving Packages
I: Validating Packages
I: Resolving dependencies of required packages...
I: Resolving dependencies of base packages...
I: Checking component main on http://
...
I: Running command: chroot bullseye2-arm64 /debootstrap/
I: Installing core packages...
...
I: Unpacking the base system...
...
I: Configuring libc-bin...
I: Base system installed successfully.
$ sudo chroot bullseye2-arm64/ /sbin/ldconfig -v lib/aarch64- linux-gnu: No such file or directory aarch64- linux-gnu' given more than once linux-gnu' given more than once aarch64- linux-gnu' given more than once linux-gnu:
libSegFault. so -> libSegFault.so linux-gnu/ ld-2.31. so is the dynamic linker, ignoring
/sbin/ldconfig: Can't stat /usr/local/
/sbin/ldconfig: Path `/usr/lib/
/sbin/ldconfig: Path `/lib/aarch64-
/sbin/ldconfig: Path `/usr/lib/
/sbin/ldconfig: Path `/usr/lib' given more than once
/lib/aarch64-
...
/sbin/ldconfig: /lib/aarch64-
...
/usr/local/lib:
/lib:
Seemingly now working - so now I am extremely confused :s
I'll retest on my colleagues PC tomorrow !