Hi, Quoting Giovanni Mascellani (2019-09-14 08:27:19) > Il 13/09/19 23:20, Johannes Schauer ha scritto: > > you write that support for the foreign executable is available in the > > container > > as well. If so, then why does arch-test determine that armhf cannot be > > executed? > Maybe "support for foreign executable" was not the right choice of words: it > still goes through qemu-user, so it is excluded by arch-test called with -n > (as mmdebstrap does). So execution of foreign executables is available, > meaning that the kernel is configured through binfmt_misc to reroute them to > qemu-user, but binfmt_misc is not visible inside the container. arch-test > detects them in the same way it does outside of the container: with -n it > only sees native archs, but without it perfectly sees the qemu-user (and > wine) ones.
ah okay, great! Then I think there is an even better solution. I guess mmdebstrap should first run "arch-test" (without the -n) to check if support exists without qemu-user emulation. Only if that does *not* work, should mmdebstrap run "arch-test -n" and then check /proc for possible problem reasons. Thanks! cheers, josch
signature.asc
Description: signature
