From: ludo@gnu.org (Ludovic Courtès)
To: Marius Bakke <mbakke@fastmail.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: ‘core-updates’ is back!
Date: Sat, 02 Sep 2017 23:01:11 +0200 [thread overview]
Message-ID: <87ziacvmqw.fsf@gnu.org> (raw)
In-Reply-To: <87tw0nk8oq.fsf@fastmail.com> (Marius Bakke's message of "Thu, 31 Aug 2017 18:23:33 +0200")
Hey Marius,
Marius Bakke <mbakke@fastmail.com> 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 <mbakke@fastmail.com>
> Date: Thu, 31 Aug 2017 18:13:08 +0200
> Subject: [PATCH] gnu: gcc@6: 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’.
next prev parent reply other threads:[~2017-09-02 21:01 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-28 22:01 ‘core-updates’ is back! Ludovic Courtès
2017-08-29 8:44 ` Efraim Flashner
2017-08-30 9:30 ` Efraim Flashner
2017-08-30 19:10 ` Marius Bakke
2017-08-30 20:16 ` Efraim Flashner
2017-08-30 20:37 ` Marius Bakke
2017-08-31 14:44 ` Ludovic Courtès
2017-08-31 16:23 ` Marius Bakke
2017-08-31 17:18 ` Marius Bakke
2017-09-02 11:18 ` Marius Bakke
2017-09-02 21:01 ` Ludovic Courtès [this message]
2017-08-30 21:17 ` Ricardo Wurmus
2017-08-30 21:51 ` Marius Bakke
2017-08-29 9:14 ` Andy Wingo
2017-08-29 10:01 ` Ricardo Wurmus
2017-08-29 13:36 ` 宋文武
2017-08-30 9:58 ` Ludovic Courtès
2017-08-30 9:58 ` Ludovic Courtès
2017-09-05 13:21 ` Ricardo Wurmus
2017-09-05 14:57 ` bug#26048: " Ludovic Courtès
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=87ziacvmqw.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=mbakke@fastmail.com \
/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.