From mboxrd@z Thu Jan  1 00:00:00 1970
From: ludo@gnu.org (Ludovic =?utf-8?Q?Court=C3=A8s?=)
Subject: Re: =?utf-8?Q?=E2=80=98core-updates=E2=80=99?= is back!
Date: Thu, 31 Aug 2017 16:44:18 +0200
Message-ID: <87y3pzokzh.fsf@gnu.org>
References: <878ti3uzaz.fsf@gnu.org>
	<20170829084453.GJ1618@macbook42.flashner.co.il>
	<20170830093016.GP1618@macbook42.flashner.co.il>
	<87fuc8lvm5.fsf@fastmail.com>
	<20170830201607.GB2353@macbook42.flashner.co.il>
	<87a82glrlc.fsf@fastmail.com>
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]:49690)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <ludo@gnu.org>) id 1dnQhm-0006zK-El
	for guix-devel@gnu.org; Thu, 31 Aug 2017 10:44:27 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <ludo@gnu.org>) id 1dnQhh-0006qq-PT
	for guix-devel@gnu.org; Thu, 31 Aug 2017 10:44:26 -0400
In-Reply-To: <87a82glrlc.fsf@fastmail.com> (Marius Bakke's message of "Wed, 30
	Aug 2017 22:37:35 +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" <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
To: Marius Bakke <mbakke@fastmail.com>
Cc: guix-devel <guix-devel@gnu.org>

Marius Bakke <mbakke@fastmail.com> skribis:

> Efraim Flashner <efraim@flashner.co.il> writes:
>
>> On Wed, Aug 30, 2017 at 09:10:42PM +0200, Marius Bakke wrote:
>>> Since we're on the topic, I would like to switch to GCC 6 or 7 soon...
>>> Are we agile enough to use the very latest GCC by default yet? :-)
>>
>> That would be nice to at least move to GCC 6. My aarch64 board is
>> currently idle, I can see how well it works on my machine.
>
> The main issue with GCC 6 is that we need to port the SOURCE_DATE_EPOCH
> patches again.  But we might want to do that even if switching to 7.

I think we should upgrade.  My preference would be GCC 6, which I think
may trigger fewer build failures than GCC 7, but maybe GCC 7 would be
fine.

Are you sure the SOURCE_DATE_EPOCH thing isn=E2=80=99t already in GCC 6?

Thanks,
Ludo=E2=80=99.