when building libgdx on alpine linux on aarch64 (with a patch to build for current architecture instead of cross-compiling), whenever g++ gets invoked, there seems to be some chance that instead of g++ starting, nothing happens at all and ant seems to be stuck in futex_wait (possibly waiting for g++ to exit, but since g++ didn't even start...)

when using qemu user mode emulation on an x86_64 machine, the chance that a call to g++ instead freezes the process seems to be low enough that sometimes the whole build gets through, while on a native aarch64 device (msm8998, mainline Linux not android) only about 0-4 c++ files get compiled to object files before the hang occurs. Running natively on x86_64, I never saw this issue (musl or otherwise)

in case it's related, the environment is an aarch64 chroot (architectural one on the x86_64 machine) with alpine linux (so musl libc).