From: Mark H Weaver <mhw@netris.org>
To: Andreas Enge <andreas@enge.fr>
Cc: guix-devel@gnu.org
Subject: Re: python-3.3.5 test failures on i686 in core-updates
Date: Wed, 17 Sep 2014 07:27:21 -0400 [thread overview]
Message-ID: <87ha06sd0m.fsf@yeeloong.lan> (raw)
In-Reply-To: <20140917110220.GB8046@debian.surfnet.iacbox> (Andreas Enge's message of "Wed, 17 Sep 2014 13:02:20 +0200")
Andreas Enge <andreas@enge.fr> writes:
> On Wed, Sep 17, 2014 at 12:10:24PM +0200, Ludovic Courtès wrote:
>> So now we have two option:
>> 1. Patch GCC 4.8.3 in core-updates, and rebuild the whole thing.
>> 2. Switch to GCC 4.9 as the default.
>> Option #1 is the safest, I think.
>
> As we need to rebuild everything anyway, how about trying out option 2?
We'd need to fix the GCC 4.9 build on mips64el first.
> In any case, before doing that, we should merge core-updates back to activate
> the security fix for glibc.
Given how broken things currently are on i686 in core-updates (broken
setresuid/setresgid in glibc => python-3 test failures => hundreds of
dependency failures of other important packages including emacs), I
don't see this as a good option for i686 users.
At minimum, we'd need to disable python-3 tests for i686, but even so, I
wonder what else will be broken due to the faulty setresuid/setresgid in
glibc.
Mark
prev parent reply other threads:[~2014-09-17 11:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-16 17:44 python-3.3.5 test failures on i686 in core-updates Mark H Weaver
2014-09-16 21:53 ` Mark H Weaver
2014-09-17 10:10 ` Ludovic Courtès
2014-09-17 10:49 ` Mark H Weaver
2014-09-17 11:47 ` Ludovic Courtès
2014-09-17 13:52 ` Mark H Weaver
2014-09-17 15:22 ` Ludovic Courtès
2014-09-17 16:45 ` Eric Bavier
2014-09-17 21:11 ` Ludovic Courtès
2014-09-17 11:02 ` Andreas Enge
2014-09-17 11:27 ` Mark H Weaver [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=87ha06sd0m.fsf@yeeloong.lan \
--to=mhw@netris.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 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.