From: Mark H Weaver <mhw@netris.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: python-3.3.5 test failures on i686 in core-updates
Date: Wed, 17 Sep 2014 09:52:01 -0400 [thread overview]
Message-ID: <87mw9ypd6m.fsf@yeeloong.lan> (raw)
In-Reply-To: <87ppeua2py.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Wed, 17 Sep 2014 13:47:05 +0200")
ludo@gnu.org (Ludovic Courtès) writes:
> Mark H Weaver <mhw@netris.org> skribis:
>
>> ludo@gnu.org (Ludovic Courtès) writes:
>
> [...]
>
>>> It turned out to be a GCC 4.8 bug:
>>>
>>> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61801
>>>
>>> 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.
>>>
>>> Thoughts?
>>
>> We've not yet built GCC 4.9.x successfully on mips64el, so that leads me
>> to prefer option #1.
>
> OK, let’s do option #1 so we can merge core-updates ASAP.
>
> Mark: could you add the relevant patch in core-updates?
Okay, but I have other plans today and won't be able to do this for at
least 12 hours. It would be great if someone else could do it sooner
and start another core-updates evaluation on hydra, but otherwise I'll
do it when I can.
Mark
next prev parent reply other threads:[~2014-09-17 13:54 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 [this message]
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
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=87mw9ypd6m.fsf@yeeloong.lan \
--to=mhw@netris.org \
--cc=guix-devel@gnu.org \
--cc=ludo@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).