From: Chris Marusich <cmmarusich@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>,
"Efraim Flashner" <efraim@flashner.co.il>
Cc: guix-devel@gnu.org
Subject: Re: I've rebased wip-ppc64le onto core-updates
Date: Thu, 11 Mar 2021 00:24:25 -0800 [thread overview]
Message-ID: <87eegm3xom.fsf_-_@gmail.com> (raw)
In-Reply-To: <87czw75n4x.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Wed, 10 Mar 2021 11:17:02 +0100, Wed, 10 Mar 2021 12:37:28 +0200")
[-- Attachment #1: Type: text/plain, Size: 2752 bytes --]
Hi,
I've rebased wip-ppc64le again just now onto the latest core-updates.
There were no conflicts.
Because I committed 5d2863dfe4613d5091e61800fcd5a48922c8ce4e and
001fc29b43fd0beb365d536774fae96624309413 directly to core-updates before
rebasing, I removed some similar commits from wip-ppc64le that are no
longer needed. The rest is the same as before.
Ludovic Courtès <ludo@gnu.org> writes:
> We’ll have to think about merging. At things stand, it seems that the
> bits that could go to ‘master’ (those that don’t trigger a world
> rebuild) are already there, right?
>
> For the rest, we could aim for rebasing on core-updates and merging
> there.
Essentially, yes. The current plan is to periodically rebase
wip-ppc64le onto core-updates while working out the last few
powerpc64le-linux issues, then merge wip-ppc64le into core-updates, and
then merge core-updates into master.
I've taken care to only include in wip-ppc64le those commits that are
relevant to the porting effort. Although there are some minor commits
on wip-ppc64le that could be cherry-picked onto master, I'm not sure
it's necessary or particularly helpful to go out of our way to do that
right now. I would prefer to just finish the wip-ppc64le branch, merge
it into core-updates, and then merge core-updates into master.
Efraim Flashner <efraim@flashner.co.il> writes:
> As noted in another thread this would involve updating gcc to gcc-8.
> There are some other patches which could go straight into master (I'm
> looking at libelf specifically, probably others), but glibc and
> gcc/libstdc++ I'm not sure how to do those ones.
>
> Actually, looking at the branch there's also findutils-boot0, but that
> can be changed to only be for target-powerpc for now and changed in
> core-updates. I have a similar one I had to do for binutils on
> powerpc-linux that I managed to make not affect other architectures.
The libelf fix (b13ba3e gnu: libelf: Fix compilation for
powerpc64le-linux) could go to master, but it's a no-op for all systems
other than powerpc64le-linux. Since nobody is using the
powerpc64le-linux port yet, there is no need for that change to go to
master at this time.
The findutils-boot0 fix (f4cbd18 gnu: commencement: Fix findutils-boot0
on some systems) fixes findutils-boot0 not only for powerpc64le-linux,
but for any system that does not use glibc-mesboot (i.e., any system
other than x86_64-linux or i686-linux). We could limit the change to
just fix it for powerpc64le-linux, but I think the other systems will
need the fix, too.
In short, I think it will be simplest to just merge wip-ppc64le into
core-updates and then merge core-updates into master.
--
Chris
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2021-03-11 8:24 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2021-03-02 14:51 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 ` Release on April 18th? zimoun
2021-03-10 15:30 ` 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
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=87eegm3xom.fsf_-_@gmail.com \
--to=cmmarusich@gmail.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 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.