Re: Cross arm*-musl hangs when runing g-ir-scanner-qemuwrapper

[voidlinux-github@inbox.vuxu.org]

[-- Attachment #1: Type: text/plain, Size: 1279 bytes --]

New comment by newbluemoon on void-packages repository

https://github.com/void-linux/void-packages/issues/11426#issuecomment-489439856
Comment:
I did some more digging:

There is a temporary directory `/builddir/webkitgtk-2.24.1/build/Source/WebKit/tmp-<something>` (it gets deleted when the build is aborted) with an executable `WebKit2-4.0` which is executed basically as

`./WebKit2-4.0 --introspect-dump=functions.txt,dump.xml`

which yields the introspection data.

Copied to my Raspberry Pi and executed everything is fine. However, when run with `qemu-arm-static` the output file `dump.xml` is truncated, or to be more precise, running `./WebKit2-4.0` just doesn’t continue and hangs.

So I chrooted into the masterdir and ran

`qemu-arm-static -d unimp -E LD_LIBRARY_PATH="/usr/armv7l-linux-musleabihf/usr/lib" -L "/usr/armv7l-linux-musleabihf" ./WebKit2-4.0 --introspect-dump=functions.txt,dump.xml`

manually and got

`Unsupported syscall: 389`

which is the `membarrier` syscall which if I recall correctly musl started using with 1.1.22.

So could this be the culprit? But then I have no idea why it’s working for @pullmoll (maybe it’s random?).
For me x86_64 host --> x86_64 chroot --> armv7l-musl target also doesn’t work.