On 12/01/2017 06:31 PM, Eric Blake wrote: > It sounds like you aren't on a bare-metal sh4 machine, but rather that you > are on a VM, and that your VM has tripped up on a qemu emulation bug. As > such, the > fix to your problem is to get the qemu folks to figure out why sh4 isn't > being emulated correctly, and is not really something that m4 is at fault for > (other > than m4 managed to trigger the non-emulated syscall).
The cause of this problem is already known. It's a limitation in QEMU which was exposed due to a recent change in glibc upstream. The issue has already been resolved and there is no bug in m4 or other packages. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
