unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: Chris Marusich <cmmarusich@gmail.com>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: Release on April 18th?
Date: Wed, 10 Mar 2021 14:27:47 +0100	[thread overview]
Message-ID: <86sg53cf58.fsf@gmail.com> (raw)
In-Reply-To: <87im6042fr.fsf@gmail.com>

Hi Chris,

On Tue, 09 Mar 2021 at 10:17, Chris Marusich <cmmarusich@gmail.com> wrote:
> zimoun <zimon.toutoune@gmail.com> writes:
>
>> Is it doable to have core-updates merged in the next weeks?  Or not at
>> all.
>
> Do we plan to upgrade GCC?  This is required for the powerpc64le-linux
> port; see below for details.

You mean replace gcc-7 by gcc-8 or greater, right?  It implies a
core-updates merge, right?


> The wip-ppc64le branch, which ports Guix to an architecture that can be
> run on freedom-friendly POWER9 systems like the Talos II and Blackbird
> from Raptor Computing Systems, is "almost" done, and I would really like
> to try to get it into the next release if possible.

Could be cool!

> However, there is still some work to do, and I wouldn't necessarily want
> to block the release just for sake of the powerpc64le-linux port.
>
> In fact, the wip-ppc64le branch was "fully functional" for a little
> while.  By "fully functional," I mean that "make check" succeeded, "make
> guix-binary.powerpc64le-linux.tar.xz" succeeded, the resulting binary
> could be installed on a fresh Debian ppc64le system, the binary could
> successfully build and run GNU Hello, and the binary could successfully
> run "guix pull", and the newly installed "guix pull" could do the same.
>
> However, that was using glibc 2.31.  On core-updates, glibc has been
> updated to 2.32, which unfortunately breaks wip-ppc64le.  To fix it, we
> must upgrade GCC from 7 to 8 (or greater), and that is what we have done
> on the wip-ppc64le branch (upgrade GCC to 8).  Currently, we are working
> through build failures that occurred as a result, but I'm optimistic that
> we can resolve those in the coming weeks.

Thanks for the explanations.


> The real question, I think, is when do we plan to upgrade GCC on
> core-updates?  It's still on GCC 7.5.0.  The powerpc64le-linux port will
> require GCC 8 or greater, since core-updates is now using glibc 2.32.

Does it make sense to merge wip-ppc64le and core-updates?


Cheers,
simon


  parent reply	other threads:[~2021-03-10 13:29 UTC|newest]

Thread overview: 64+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-02 14:51 Release on April 18th? zimoun
2021-03-02 16:00 ` Julien Lepiller
2021-03-02 20:03 ` Leo Famulari
2021-03-05 14:31   ` Andreas Enge
2021-03-05 19:27     ` Leo Famulari
2021-03-05 20:20       ` zimoun
2021-03-05 20:58         ` Leo Famulari
2021-03-05 23:57           ` zimoun
2021-03-06 20:14           ` Tobias Geerinckx-Rice
2021-03-03 14:16 ` Ludovic Courtès
2021-03-03 18:51   ` Leo Famulari
2021-03-04  9:41     ` zimoun
2021-03-04 19:07       ` Leo Famulari
2021-03-04 22:18         ` zimoun
2021-03-04 22:43           ` Leo Famulari
2021-03-05 20:19     ` Leo Famulari
2021-03-05 23:58       ` zimoun
2021-03-06 18:56         ` Leo Famulari
2021-03-06 19:06     ` Leo Famulari
2021-03-06 23:22       ` Leo Famulari
2021-03-07  3:51         ` Raghav Gururajan
2021-03-07  5:39           ` Raghav Gururajan
2021-03-07 20:44             ` Leo Famulari
2021-03-07 20:56               ` Raghav Gururajan
2021-03-07 20:50             ` Leo Famulari
2021-03-08  9:38       ` zimoun
2021-03-05 20:21   ` Leo Famulari
2021-03-09 18:17 ` Chris Marusich
2021-03-09 21:32   ` Vincent Legoll
2021-03-10  8:30     ` Release on April 18th? (ppc64le support specifically) Efraim Flashner
2021-03-11  9:10     ` Release on April 18th? Chris Marusich
2021-03-12  8:02       ` Vincent Legoll
2021-03-12 18:42         ` Chris Marusich
2021-03-12 18:52           ` Chris Marusich
2021-03-14 12:31           ` Vincent Legoll
2021-03-15 16:36           ` Ludovic Courtès
2021-03-16  4:03           ` Let's include powerpc64le-linux in the next release (was: Re: Release on April 18th?) Chris Marusich
2021-03-16  7:08             ` Efraim Flashner
2021-03-16  8:10               ` Léo Le Bouter
2021-03-23 13:42             ` Let's include powerpc64le-linux in the next release Ludovic Courtès
2021-03-23 13:47               ` Léo Le Bouter
2021-03-23 14:01               ` Tobias Geerinckx-Rice
2021-03-30  8:23                 ` Ludovic Courtès
2021-03-30 22:20                   ` Vincent Legoll
2021-03-23 17:09               ` Let's include powerpc64le-linux in the next release, " Chris Marusich
2021-03-10 13:27   ` zimoun [this message]
2021-03-10 15:30     ` Release on April 18th? Efraim Flashner
2021-03-10 15:59       ` zimoun
2021-03-10 18:33         ` Efraim Flashner
2021-03-11  8:58       ` Chris Marusich
2021-03-11 13:30         ` Efraim Flashner
2021-03-12  8:33           ` Chris Marusich
2021-03-12 10:11             ` Andreas Enge
2021-03-12 13:43             ` Efraim Flashner
  -- strict thread matches above, loose matches on Subject: below --
2021-02-28  6:53 I've rebased wip-ppc64le onto core-updates Chris Marusich
2021-02-28 20:42 ` Léo Le Bouter
2021-03-01 19:14   ` Tobias Platen
2021-03-01 21:36   ` jbranso
2021-03-10 10:17 ` Ludovic Courtès
2021-03-10 10:37   ` Efraim Flashner
2021-03-11  8:24   ` Chris Marusich
2021-03-11  8:37     ` Léo Le Bouter
2021-03-15 16:25     ` Ludovic Courtès
2021-03-16  4:26       ` I've rebased wip-ppc64le onto core-updates, Re: Release on April 18th? Chris Marusich

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=86sg53cf58.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=cmmarusich@gmail.com \
    --cc=guix-devel@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).