On Tue, 2021-08-31 at 15:40 +0200, Frans de Boer wrote:
To that end, I already had made sure that /bin/bash exist for real and that /bin is no link to /usr/bin. Also, the tools I use are bash scripts, which calls other bash scripts without problem - in any /bin configuration. I even made bash statically linked, just like most other tools. All to no avail.
So, you can run /bin/bash in your chroot? Because it looks in your output as if no shell ever starts. I'd suspected some missing shared library, but if it also happens for statically linked bash, there must be some other - probably similar - reason. By design, "configure" is written in a shell dialect that's portable to the maximum possible extent. Your shell can't possibly be too old for it - it's broken. TBH, I you are causing yourself lots of trouble by your use of chroot and statically linked binaries. Why not just use a container?
sudo podman run --rm --privileged --net none multiarch/qemu-user- static --reset -p yes Setting /usr/bin/qemu-aarch64-static as binfmt interpreter for aarch64 podman run --quiet -it --rm --arch=arm64 registry.opensuse.org/opensuse/leap:15.3 :/ # grep CPE /etc/os-release CPE_NAME="cpe:/o:opensuse:leap:15.3" :/ # uname -a Linux edbe550e5ede 5.13.12-2-default #1 SMP Fri Aug 20 07:04:28 UTC 2021 (33df9c6) aarch64 aarch64 aarch64 GNU/Linux
This is almost about as easy as it gets, and every binary from Leap/aarch64 can be installed by regular means and "just works". Once the issue with qemu-binfmt is fixed, it would even work with the regular openSUSE version of qemu. Regards Martin