On 8/30/21 22:35, Martin Wilck wrote:
-----Original Message----- From: Frans de Boer
Sent: 26 August 2021 15:22 To: opensuse-factory@opensuse.org Subject: qemu-aarch64-static LS,
I can't find the qemu-aarch64-static with the available qemu version. Where can I get it? If you need 'qemu-aarch64', it is in 'qemu-linux-user' package.
Guillaume I just found out that qemu-aarch64 is indeed statically linked. The ´qemu-aarch64-binfmt' is a soft link to qemu-binfm, which itself is also statically linked. So, I guessed that I needed qemu-binfmt within
On 8/30/21 09:28, Guillaume Gardet wrote: > Hi, the chroot jail to deal with the different magic file numbers for aarch64 executables. Under openSUSE, qemu-binfmt is not a qemu executable. It is just a tiny wrapper that mangles argv[0] and starts the actual emulator, qemu- aarch64. qemu-binfmt's only purpose is to fix argv[0] to hide the
On Mon, 2021-08-30 at 21:09 +0200, Frans de Boer wrote: presence of the emulator and make the process look like a native one. (see https://build.opensuse.org/package/view_file/Virtualization/qemu/linux-user-...) AFAIK, this is a openSUSE peculiarity.
In your chroot, you need both these binaries. I recently filed a bug about this, 1186256.
Regards Martin Ok, thnx. I also copied the TW supplied qemu-aarch64 into the jail and now it starts-up.
However, configure - from multiple packages - still complains about the outdated shell version, while previously compiled aarch64 programs are just running in the jail. TW has no pre-compiled bash shell for aarch64, but from what I see in trace output, configure get the proper version data, but does not recognize it. But maybe someone with intimate knowledge about the inner workings of the configure script can decrypt the attached trace output? Command was 'bash -x ./configure 2>&1 | tee db.txt' --- Frans