all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: 49367-done@debbugs.gnu.org
Subject: bug#49367: Bootstrap binaries affected by spawni.c bug in glibc <= 2.26
Date: Sun, 04 Jul 2021 00:11:05 +0200	[thread overview]
Message-ID: <87mtr3xd3a.fsf@gnu.org> (raw)
In-Reply-To: <87y2anxf5e.fsf@inria.fr> ("Ludovic Courtès"'s message of "Sat, 03 Jul 2021 23:26:37 +0200")

Hi,

Ludovic Courtès <ludo@gnu.org> skribis:

> While building ‘findutils-boot0’ & co. for AArch64 on ci.guix, where
> some of the aarch64-linux nodes are emulated, I hit failures like this
> one a few times:
>
> starting phase `build'
> make: ../sysdeps/unix/sysv/linux/spawni.c:360: __spawnix: Assertion `ec >= 0' failed.
> qemu: uncaught target signal 6 (Aborted) - core dumped
> error: in phase 'build': uncaught exception:
> srfi-34 #<condition &invoke-error [program: "make" arguments: ("-j" "24") exit-status: #f term-signal: 6 stop-signal: #f] 149e880> 
> phase `build' failed after 0.1 seconds
> command "make" "-j" "24" failed with signal 6
> builder for `/gnu/store/rkkgavlyvf06sfdnxlfqb11bljf989y1-findutils-boot0-4.8.0.drv' failed with exit code 1

[...]

>   2. Build ‘make-boot0’ with ‘--disable-posix-spawn’.  Best solution in
>      my view.

Done in f436723ce7da2f5e752f5f4b6f0d568a7bea4403!

Note that this problem is already present in current ‘master’.  Note
also that on x86 we ‘make-boot0’ is built against glibc-mesboot0-2.16,
which is much older and isn’t affected by the ‘posix_spawn’ bug, AFAICS.

Ludo’.




      reply	other threads:[~2021-07-03 22:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-03 21:26 bug#49367: Bootstrap binaries affected by spawni.c bug in glibc <= 2.26 Ludovic Courtès
2021-07-03 22:11 ` Ludovic Courtès [this message]

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87mtr3xd3a.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=49367-done@debbugs.gnu.org \
    /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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.