From: Marius Bakke <mbakke@fastmail.com>
To: "Efraim Flashner" <efraim@flashner.co.il>,
"Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: ‘core-updates’ is back!
Date: Wed, 30 Aug 2017 21:10:42 +0200 [thread overview]
Message-ID: <87fuc8lvm5.fsf@fastmail.com> (raw)
In-Reply-To: <20170830093016.GP1618@macbook42.flashner.co.il>
[-- Attachment #1: Type: text/plain, Size: 1337 bytes --]
Efraim Flashner <efraim@flashner.co.il> writes:
> On Tue, Aug 29, 2017 at 11:44:53AM +0300, Efraim Flashner wrote:
>> On Tue, Aug 29, 2017 at 12:01:40AM +0200, Ludovic Courtès wrote:
>> > Hello Guix!
>> >
>> > Yup, I just created a new ‘core-updates’ branch by pushing
>> > <https://bugs.gnu.org/27849>. Enjoy!
>> >
>> > Let’s freeze in one month, say Oct. 1st?
>> >
>> > Ludo’.
>> >
>>
>> Lets also have a reminder about a week before to make sure we get things
>> like tzdata.
>>
>> I'm currently test building texinfo@6.4. I tried a blind update of
>> glibc, binutils, texinfo and grep but it failed during building a gcc,
>> so now i'm breaking it into smaller chunks.
>>
>
> It looks like binutils@2.29.1 is coming mid-September¹ so I'm not
> touching binutils for now. I'm not sure why updating glibc is causing
> gcc to fail to build.
Can you post the glibc update patch?
Probably unrelated, but we also have to change the '--enable-kernel'
configure flag to say '3.2.0' since that is the minimum supported by
glibc 2.26.
Also, one month, yay! Hopefully a shorter schedule will reduce the
amount of build issues during each round.
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? :-)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2017-08-30 19:10 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 [this message]
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
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
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=87fuc8lvm5.fsf@fastmail.com \
--to=mbakke@fastmail.com \
--cc=efraim@flashner.co.il \
--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).