From: ludo@gnu.org (Ludovic Courtès)
To: Andreas Enge <andreas@enge.fr>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: ‘core-updates’ freeze approaching!
Date: Fri, 18 Sep 2015 11:22:48 +0200 [thread overview]
Message-ID: <87io78xes7.fsf@gnu.org> (raw)
In-Reply-To: <20150917214315.GA31972@debian> (Andreas Enge's message of "Thu, 17 Sep 2015 23:43:15 +0200")
Andreas Enge <andreas@enge.fr> skribis:
> On Thu, Sep 17, 2015 at 10:02:08PM +0200, Ludovic Courtès wrote:
>> https://bugs.freedesktop.org/show_bug.cgi?id=92027
>
> The segfault and the valgrind issue happen in different files, so they
> do not seem to be related.
[...]
> I also tried to cd into /tmp/nix-build-..., source the environment variables
> and run "make check"; then all tests pass (but the build is for i686-linux
> on an x86_64-machine, so maybe this does not mean much outside the guix build
> container?).
With the patch applied (the patch I attached to the above bug report),
the problem indeed vanishes when outside of the build container, like
you describe.
Without the patch the problem is 100% reproducible both inside and
outside of the build container.
Ludo’.
next prev parent reply other threads:[~2015-09-18 9:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-10 13:47 ‘core-updates’ freeze approaching! Ludovic Courtès
2015-09-11 21:22 ` Ludovic Courtès
2015-09-14 15:28 ` Ludovic Courtès
2015-09-17 20:02 ` Ludovic Courtès
2015-09-17 21:43 ` Andreas Enge
2015-09-18 9:22 ` Ludovic Courtès [this message]
2015-09-26 13:14 ` ‘core-updates’ merged! Ludovic Courtès
2015-09-26 19:55 ` Substitutes available for ARM! 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=87io78xes7.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=andreas@enge.fr \
--cc=guix-devel@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 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).