Re: ‘core-updates’ is back!

[Ludovic Courtès]

Hey Marius,

Marius Bakke <address@hidden> skribis:

> However I tried cherry-picking the two commits and there was only one
> trivial conflict in gcc/c-family/c-common.h (apart from ChangeLog
> updates, which were omitted).  Patch attached and building!

Woohoo!

> I also prefer going through GCC 6 before 7.  Let's go for it, assuming
> this patch works.
>
> From 329e016e35c51426ccf30aa2335bfd3ef12678a6 Mon Sep 17 00:00:00 2001
> From: Marius Bakke <address@hidden>
> Date: Thu, 31 Aug 2017 18:13:08 +0200
> Subject: [PATCH] gnu: address@hidden: Respect SOURCE_DATE_EPOCH in __DATE__ 
> and
>  __TIME__ macros.
>
> * gnu/packages/patches/gcc-6-source-date-epoch-1.patch,
> gnu/packages/patches/gcc-6-source-date-epoch-2.patch: New files.
> * gnu/local.mk (dist_patch_DATA): Register them.
> * gnu/packages/gcc.scm (gcc-6)[source]: Use them.

Looks OK to me for your favorite branch!  (Could be both ‘master’ and
‘core-updates’ after all.)

For the switch to GCC 6 in ‘core-updates’, you can get inspiration from
commit b810a85019ab3c4ee1f889d0751b8eb06157dadc, and then do something
like “guix build sed” for testing.

Ludo’.