11.11.2014 11:02, Michal Suchanek wrote: [] > > I found that I have qemu-user-static instead of qemu-user-binfmt on > system where this works. I can run armhf binaries on a PC but the
Yes, I've seen that. > reverse does not work. There is a handler for PC binaries registered but > bash still reports it cannot execute binary file. > > Is the magic for PC binaries correct? How do I check? I replied to that at the time, -- the same magic strings are used in both packages (qemu-user-static and qemu-user-binfmt), these are generated (using simple substitutions) from a common file. >> Hello Michal. A friendly ping? Do you have any additional information >> for this bugreport? I can't do anything with it without your input... > > I did send another email in the bug report, right? Yes, and I replied to that, see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763043#22 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 ? Did you try using -user-binfmt on PC to run arm binaries, does that work? (I can try that myself, but I think I verified this). Please note that -user-binfmt (the non-statically-linked variant) will not work in a foreign chroot, since it needs not only the qemu binary itself, but also all the libraries which are linked dynamically into it. But I think this does not apply since you don't run foreign binaries in a chroot, at least as far as I can understand. Thanks, /mjt -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
