Public bug reported:
On exec of an armv7 qemu chroot on my local x86_64 desktop, launched via
/usr/sbin/qemu-binfmt-conf.sh
from
qemu-linux-user-2.9.0-374.1.x86_64
on the host, inside the chroot any compile activity is laced with
repetitions of
qemu: Unsupported syscal
fyi, similar seen for Raspbian9:
https://bugs.launchpad.net/raspbian/+bug/1732556
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1659901
Title:
Regression: SIGSEGV running Java
Status in QEMU:
N
The statically linked qemu files in chroot are cp'd from the host env
file $(which qemu-arm) $(which qemu-arm-binfmt)
/usr/bin/qemu-arm:ELF 64-bit LSB executable, x86-64,
version 1 (GNU/Linux), statically linked, for GNU/Linux 3.0.0,
BuildID[sha1]=a6c50ab9b8f1845d
> Can you just run /usr/bin/qemu-arm-static --version in the chroot,
please ? (or whatever suse calls its statically linked binary).
Yep, as soon as I'm sitting back in front of the machine with the chroot
on it. Bit later ...
> The other interesting question is what version of the (host) kern
> run /usr/bin/qemu-arm-static --version in the chroot
:/# /usr/bin/qemu-arm --version
qemu-arm version 2.10.1
Copyright (c) 2003-2017 Fabrice Bellard and the QEMU Project developers
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscr
