11.11.2014 17:07, Michal Suchanek wrote: > Excerpts from Michael Tokarev's message of Tue Nov 11 14:16:23 +0100 2014: >> 11.11.2014 13:18, Michal Suchanek wrote: >> [] >>>> So, to rehash, do I understand it right that you're having >>>> probs with running x86 binaries on arm, when using -user-binfmt >>>> but not when using -user-static ? >>> >>> I am having problem running x86 binaries on arm with either package. >> >> Aha. That is entirely different thing. Retitling the bugreport >> accordingly. Please correct me if I'm wrong. > > That's not entirely true. It only fails for static binaries and I > happened to have a statically linked application. I am able to run full > x86 wine at racing snail speed. Probably because it's dynamically > linked.
Does it help if you invoke qemu-x86_64[-static] to run your non-working executables, like, say, qemu-x86_64 /usr/bin/cdebootstrap-static ? This way we'll know if it is binfmt registration which is broken or qemu. It might sure be some missing binfmt bits. [] >>> # unrar /? >>> qemu: uncaught target signal 11 (Segmentation fault) - core dumped >>> Segmentation fault >>> >>> # apt-get install cdebootstrap-static:amd64 >>> >>> # cdebootstrap-static /? >>> -bash: /usr/bin/cdebootstrap-static: cannot execute binary file What is the version of unrar and cdebootstrap-static? I want to reproduce the problem so that it's possible to go from here. Please note that x86 qemu user target is one of less tested targets, because it is rather uncommon to run x86 hw on non-x86 platform, usually it is the opposite. Thanks, /mjt -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
