Re: [Qemu-devel] /usr/bin/m4: internal error detected

2017-12-01 Thread Andreas Schwab
On Dez 01 2017, John Paul Adrian Glaubitz wrote: > 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]. It's a

Re: [Qemu-devel] /usr/bin/m4: internal error detected

2017-12-01 Thread Florian Weimer
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

Re: [Qemu-devel] /usr/bin/m4: internal error detected

2017-12-01 Thread Florian Weimer
On 12/01/2017 12:58 PM, John Paul Adrian Glaubitz wrote: The fix is already in the packaging source of Debian's glibc [1] after I reported the bug. But the updated package has not been uploaded to the FTP servers yet. I'll ask Debian's glibc maintainers to push it. Okay. Based on the other

Re: [Qemu-devel] /usr/bin/m4: internal error detected

2017-12-01 Thread John Paul Adrian Glaubitz
Hi Florian! On 12/01/2017 11:40 AM, Florian Weimer wrote: Is this ?  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. You're right, this is indeed fixed by your patch. I

Re: [Qemu-devel] /usr/bin/m4: internal error detected

2017-12-01 Thread John Paul Adrian Glaubitz
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;

Re: [Qemu-devel] /usr/bin/m4: internal error detected

2017-12-01 Thread John Paul Adrian Glaubitz
On 12/01/2017 01:18 PM, Andreas Schwab wrote: 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]. It's a bug in qemu-linux-user, which ignores