On 7/9/19 2:51 PM, Laurent Vivier wrote: > if you use systemctl, the parameter of "./scripts/qemu-binfmt-conf.sh" > must be "--systemd m68k" rather than "--debian".
I tried that and I now get: root@nofan:/local_scratch/sid-m68k-sbuild> chroot . chroot: failed to run command ‘/bin/bash’: No such file or directory root@nofan:/local_scratch/sid-m68k-sbuild> >> But still don't get the correct path: >> >> (sid-m68k-sbuild)root@nofan:/# sh -c 'echo $0' >> /bin/sh >> (sid-m68k-sbuild)root@nofan:/# > > Well, I've tested that, and it should work... Oh, I'm not arguing that. I'm sure the error is on my side ;). I'm just trying to find out what I'm doing wrong. -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1835839 Title: qemu-user: $0 incorrectly always reports absolute path Status in QEMU: New Bug description: We just ran into an issue with the Perl package on Debian/m68k when being built with qemu-user [1]. The problem can be boiled down to qemu-user always reporting absolute paths for the shell variable $0 no matter on how the command was invoked. A simple reproducer is this: On normal system (no emulation): root@nofan:~> sh -c 'echo $0' sh root@nofan:~> On qemu-user: (sid-m68k-sbuild)root@nofan:/# sh -c 'echo $0' /bin/sh (sid-m68k-sbuild)root@nofan:/# > [1] https://lists.debian.org/debian-68k/2019/07/msg00007.html To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1835839/+subscriptions