This is the mail archive of the
mailing list for the glibc project.
Re: /usr/bin/m4: internal error detected
- From: John Paul Adrian Glaubitz <glaubitz at physik dot fu-berlin dot de>
- To: Daniel Kahn Gillmor <dkg at fifthhorseman dot net>, bug-m4 at gnu dot org
- Cc: debian-superh at lists dot debian dot org, libc-alpha at sourceware dot org, QEMU Developers <qemu-devel at nongnu dot org>
- Date: Fri, 1 Dec 2017 10:51:11 +0100
- Subject: Re: /usr/bin/m4: internal error detected
- Authentication-results: sourceware.org; auth=none
- References: <firstname.lastname@example.org>
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 <email@example.com>: 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  and mainly affects
qemu-user which we are using for m68k and sh4 .
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.
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - firstname.lastname@example.org
`. `' Freie Universitaet Berlin - email@example.com
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913