From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 57327 invoked by alias); 1 Dec 2017 10:40:35 -0000 Mailing-List: contact libc-alpha-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: libc-alpha-owner@sourceware.org Received: (qmail 57314 invoked by uid 89); 1 Dec 2017 10:40:34 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-6.7 required=5.0 tests=BAYES_00,GIT_PATCH_2,KB_WAM_FROM_NAME_SINGLEWORD,SPF_HELO_PASS,T_RP_MATCHES_RCVD autolearn=ham version=3.3.2 spammy=Hx-spam-relays-external:sk:dhcp-19, H*r:sk:dhcp-19, H*RU:sk:dhcp-19, H*M:4009 X-HELO: mx1.redhat.com Subject: Re: /usr/bin/m4: internal error detected To: John Paul Adrian Glaubitz , Daniel Kahn Gillmor , bug-m4@gnu.org Cc: debian-superh@lists.debian.org, libc-alpha@sourceware.org, QEMU Developers References: <87po7zrq65.fsf@fifthhorseman.net> From: Florian Weimer Message-ID: <861bc28d-4009-d35e-c03b-8ae7b0ca8680@redhat.com> Date: Fri, 01 Dec 2017 10:40:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2017-12/txt/msg00012.txt.bz2 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 >> : 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 ? 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