guix-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: ‘core-updates’ is back!


From: Efraim Flashner
Subject: Re: ‘core-updates’ is back!
Date: Wed, 30 Aug 2017 23:16:07 +0300
User-agent: Mutt/1.8.3 (2017-05-23)

On Wed, Aug 30, 2017 at 09:10:42PM +0200, Marius Bakke wrote:
> Efraim Flashner <address@hidden> 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 address@hidden 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 address@hidden 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?

I didn't actually keep a patch of the update. 2.25->2.26, the 3 CVE
patches and the memchr-overflow and vectorized-strcspn get dropped. in
gnu/packages/commencement.scm I changed the two 'package/inherit' to
'package (inherit '.

> 
> 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.

I didn't change this in my patch.

> 
> 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? :-)

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.


-- 
Efraim Flashner   <address@hidden>   אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D  14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted

Attachment: signature.asc
Description: PGP signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]