From: Danny Milosavljevic <dannym@scratchpost.org>
To: ng0@n0.is, guix-devel@gnu.org, bug-guix@gnu.org
Subject: ARM compilation via qemu binfmt - Assertion failure
Date: Thu, 8 Feb 2018 17:42:38 +0100 [thread overview]
Message-ID: <20180208174238.2abc85dc@scratchpost.org> (raw)
In-Reply-To: <87k1vqv23v.fsf@abyayala.i-did-not-set--mail-host-address--so-tickle-me>
Hi ng0,
On Tue, 06 Feb 2018 10:33:56 +0000
ng0@n0.is wrote:
> recently I've read about slow but native compiling of ARM on qemu.
Unfortunately, there's a (pretty reproducible) problem with it.
guix-master/guix $ ./pre-inst-env guix system disk-image --system=armhf-linux -e "(@ (gnu system install) installation-os)"
[... building grub-2.02 ...]
phase `configure' succeeded after 821.8 seconds
starting phase `patch-generated-file-shebangs'
patch-makefile-SHELL: ./po/Makefile: changing `SHELL' from `/bin/sh' to `/gnu/st[...]
phase `patch-generated-file-shebangs' succeeded after 14.6 seconds
starting phase `build'
bison -d -p grub_script_yy -b grub_script ./grub-core/script/parser.y
flex -o grub_script.yy.c --header-file=grub_script.yy.h ./grub-core/script/yylex[...]
bison: ../sysdeps/unix/sysv/linux/spawni.c:360: __spawnix: Assertion `ec >= 0' failed
This is only fixed in glibc 2.27 (not in core-updates).
The fix is:
https://sourceware.org/bugzilla/show_bug.cgi?id=22273
diff --git a/sysdeps/unix/sysv/linux/spawni.c b/sysdeps/unix/sysv/linux/spawni.c
index dea1650..f02ac19 100644
--- a/sysdeps/unix/sysv/linux/spawni.c
+++ b/sysdeps/unix/sysv/linux/spawni.c
@@ -365,9 +365,15 @@ __spawnix (pid_t * pid, const char *file,
if (new_pid > 0)
{
ec = args.err;
- assert (ec >= 0);
if (ec != 0)
- __waitpid (new_pid, NULL, 0);
+ {
+ /* It handles the unlikely case where the auxiliary vfork process
+ is killed before calling _exit or execve. */
+ int status;
+ __waitpid (new_pid, &status, 0);
+ if (WIFSIGNALED (status))
+ ec = 0;
+ }
}
else
ec = -new_pid;
next prev parent reply other threads:[~2018-02-08 16:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87bmh4qrf5.fsf@abyayala.i-did-not-set--mail-host-address--so-tickle-me>
[not found] ` <87bmh3kbd9.fsf@gnu.org>
2018-02-06 10:33 ` GSoC ng0
2018-02-08 11:25 ` GSoC ng0
2018-02-08 12:09 ` GSoC Gábor Boskovits
2018-02-08 12:31 ` GSoC ng0
2018-02-08 12:41 ` GSoC ng0
2018-02-08 13:57 ` RISC-V port for GSoC? Ludovic Courtès
2018-02-08 14:42 ` ng0
2018-02-08 18:42 ` Ricardo Wurmus
2018-02-08 19:19 ` Gábor Boskovits
2018-02-08 19:34 ` ng0
2018-02-08 22:25 ` Ludovic Courtès
2018-02-08 16:42 ` Danny Milosavljevic [this message]
2018-02-10 23:45 ` ARM compilation via qemu binfmt - Assertion failure Chris Marusich
2018-02-11 1:07 ` bug#30394: " Leo Famulari
2018-02-11 9:53 ` Pjotr Prins
2018-02-16 10:35 ` bug#30394: " Ludovic Courtès
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180208174238.2abc85dc@scratchpost.org \
--to=dannym@scratchpost.org \
--cc=bug-guix@gnu.org \
--cc=guix-devel@gnu.org \
--cc=ng0@n0.is \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).