all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Chris Marusich <cmmarusich@gmail.com>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: guix-devel@gnu.org, bug-guix@gnu.org, ng0@n0.is
Subject: Re: ARM compilation via qemu binfmt - Assertion failure
Date: Sun, 11 Feb 2018 00:45:18 +0100	[thread overview]
Message-ID: <87fu68o1dd.fsf@gmail.com> (raw)
In-Reply-To: <20180208174238.2abc85dc@scratchpost.org> (Danny Milosavljevic's message of "Thu, 8 Feb 2018 17:42:38 +0100")

[-- Attachment #1: Type: text/plain, Size: 279 bytes --]

Danny Milosavljevic <dannym@scratchpost.org> writes:

> This is only fixed in glibc 2.27 (not in core-updates).

Should we upgrade glibc in core-updates, then?  Or is it better to do it
in the next core-updates cycle, to avoid still more unexpected breakage?

-- 
Chris

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

  reply	other threads:[~2018-02-10 23:45 UTC|newest]

Thread overview: 18+ 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     ` ARM compilation via qemu binfmt - Assertion failure Danny Milosavljevic
2018-02-10 23:45       ` Chris Marusich [this message]
2018-02-11  1:07         ` bug#30394: " Leo Famulari
2018-02-11  1:07         ` Leo Famulari
2018-02-11  9:53         ` Pjotr Prins
2018-02-16 10:35       ` bug#30394: " Ludovic Courtès
2018-02-16 10:35       ` 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

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

  git send-email \
    --in-reply-to=87fu68o1dd.fsf@gmail.com \
    --to=cmmarusich@gmail.com \
    --cc=bug-guix@gnu.org \
    --cc=dannym@scratchpost.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 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.