Hi Michael,

> >> Does the prob persist when you just re-install qemu-user-static
> >> package using dpkg (without removing it first)?  The question
> >> here is that update-binfmt does not refresh changed definitions
> >> at the first run.
> > Guess not - just before reporting the bug I upgraded to the latest 
> > experimental version, so there should've been a reinstall just before.
> 
> As far as I can see, qemu is not in experimental debian branch.
> What do you mean by "experimental version"?
I meant that I installed the latest available release - from unstable, not 
experimental. My bad.


> But anyway, I don't understand: does reinstalling qemu-user-static
> fix the problem?
Ah, *really* install once again? Simply installing once as apt-get does 
implicitly is not enough?


> > # hexdump -C -n 64 
> > debian-jessie-ppc64el/usr/lib/gcc/powerpc64le-linux-gnu/4.9/cc1.debian-bug
> > 00000000  7f 45 4c 46 02 01 01 03  00 00 00 00 00 00 00 00  
> > |.ELF............|
> > 00000010  02 00 15 00 01 00 00 00  c8 7e 11 10 00 00 00 00  
> > |.........~......|
> > 00000020  40 00 00 00 00 00 00 00  50 05 06 01 00 00 00 00  
> > |@.......P.......|
> > 00000030  02 00 00 00 40 00 38 00  09 00 40 00 1f 00 1e 00  
> > |....@.8...@.....|
> > 00000040
> 
> Binaries with this header are executed automatically by qemu of the reported
> version on my system.  Main difference of this binary from other binaries is
> the value of 03 in byte 7 (which is OSABI_GNU instead of 0 which is 
> OSABI_SYSV),
> and is is what was fixed in the last update, but due to bug in binfmt-support
> just installing new version is not sufficient, reinstall or reboot is needed.
Yes, that seems to fix the issue as well.

Thanks!

Reply via email to