From mboxrd@z Thu Jan  1 00:00:00 1970
From: Mark H Weaver <mhw@netris.org>
Subject: Re: python-3.3.5 test failures on i686 in core-updates
Date: Wed, 17 Sep 2014 06:49:05 -0400
Message-ID: <87lhpisese.fsf@yeeloong.lan>
References: <87k353tq8b.fsf@yeeloong.lan> <87fvfrtepv.fsf@yeeloong.lan>
	<8761gmblrj.fsf@gnu.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Return-path: <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:54632)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <mhw@netris.org>) id 1XUCpB-0005Rb-QT
	for guix-devel@gnu.org; Wed, 17 Sep 2014 06:51:06 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <mhw@netris.org>) id 1XUCp6-0003ox-Vi
	for guix-devel@gnu.org; Wed, 17 Sep 2014 06:51:01 -0400
In-Reply-To: <8761gmblrj.fsf@gnu.org> ("Ludovic
	\=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\=
	\=\?utf-8\?Q\?s\?\= message of "Wed, 17 Sep 2014 12:10:24 +0200")
List-Id: "Development of GNU Guix and the GNU System distribution."
	<guix-devel.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/guix-devel>
List-Post: <mailto:guix-devel@gnu.org>
List-Help: <mailto:guix-devel-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=subscribe>
Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org
Sender: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org
To: Ludovic =?utf-8?Q?Court=C3=A8s?= <ludo@gnu.org>
Cc: guix-devel@gnu.org

ludo@gnu.org (Ludovic Court=C3=A8s) writes:

> Mark H Weaver <mhw@netris.org> skribis:
>
>> I wrote:
>>> Python-3.3.5 fails its test suite on i686.
>>
>> This turns out to be a bug in glibc-2.20.
>> I've filed an upstream ticket here:
>>
>> https://sourceware.org/bugzilla/show_bug.cgi?id=3D17398
>
> It turned out to be a GCC 4.8 bug:
>
>   https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D61801
>
> 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.

    Thanks,
      Mark