Re: /usr/bin/m4: internal error detected

[Florian Weimer <fweimer at redhat dot com>]

On 12/01/2017 10:51 AM, John Paul Adrian Glaubitz wrote:
> Hi Daniel!
>
> On 12/01/2017 06:08 AM, Daniel Kahn Gillmor wrote:
> > ------------
> > Copying file po/Makefile.in.in
> > Copying file po/Makevars.template
> > qemu: Unsupported syscall: -1
> > m4: ../sysdeps/unix/sysv/linux/spawni.c:366: __spawnix: Assertion `ec 
> > >= 0' failed.
> > /usr/bin/m4: internal error detected; please report this bug to 
> > <bug-m4@gnu.org>: Aborted
> > -----------
>
> This isn't a bug in m4 or anything architecture-specific, it's a regression
> that was introduced by an upstream change in glibc [1] and mainly affects
> qemu-user which we are using for m68k and sh4 [2].
>
> While the change in glibc is most certainly correct (I don't have enough
> background knowledge to comment on that), it broke qemu-user for everyone
> and so far there is no possible fix in sight.
>
> I am CC'ing this to libc-alpha in the hope that someone from glibc upstream
> might give us a tip on how to resolve the issue. Not being able to use 
> qemu-user
> anymore is quite a deal breaker because lots of people use qemu-user for
> debugging issues on foreign architectures which is now no longer possible.

Is this <https://sourceware.org/bugzilla/show_bug.cgi?id=22273>?  If 
yes, it should be fixed in master and on the 2.25 and 2.26 branches. 
2.24 and earlier should not be affected.

Thanks,
Florian