all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Efraim Flashner <efraim@flashner.co.il>
To: Felix Lechner <felix.lechner@lease-up.com>
Cc: 61989@debbugs.gnu.org, Leo Famulari <leo@famulari.name>
Subject: [bug#61989] [PATCH 00/11] Adding Gocryptfs (feature branch)
Date: Sun, 19 Mar 2023 10:51:51 +0200	[thread overview]
Message-ID: <ZBbNJ5+Hp6ekQ3pH@3900XT> (raw)
In-Reply-To: <CAFHYt55Gh4DYv3_sSET7OuJVs8C+nZ+gyOCxpSBO+KYBgvmfag@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1663 bytes --]

On Fri, Mar 17, 2023 at 12:02:55PM -0700, Felix Lechner via Guix-patches via wrote:
> Hi Leo,
> 
> On Thu, Mar 16, 2023 at 5:00 PM Leo Famulari <leo@famulari.name> wrote:
> >
> > your next steps should be identifying Guix developers who have a history
> > of working on the PowerPC port and asking them to take a look.
> 
> Based on this blog post [1] I wrote to Efraim on IRC. I mentioned this
> bug and the connection to the powerpc64le port. Then I asked the group
> about the whereabouts of the two blog authors, namely Chris Marusich
> and Léo Le Bouter. Unfortunately I did not receive a response to
> either message.

To the best of my knowledge both Léo and Chris have both left the
project.

As it currently stands on master, go-1.19 doesn't build for ppc64le. I
mentioned on IRC that it looks like the 'patch-gcc:lib phase in go-1.17
but for ppc64le, but after trying a few different combinations it looks
to me more like the test failures on aarch64 (which I haven't looked at
in forever).

Looking at it I'm convinced that we are missing patching something on
our end, and that these tests are probably supposed to pass.

My suggestion is to skip the tests on go-1.17+ on ppc64le and adjust the
note that all the listed architectures should have their test suite
reviewed to figure out what we're missing. There's something about the
internal linking on non-x86 architectures that needs investigating.


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

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2023-03-19  8:53 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-05 20:52 [bug#61989] [PATCH 00/11] Adding Gocryptfs (feature branch) Felix Lechner via Guix-patches via
2023-03-05 20:54 ` [bug#61989] [PATCH 01/11] gnu: go-golang-org-x-sys: Update to 0.4.0 Felix Lechner via Guix-patches via
2023-03-05 20:54 ` [bug#61989] [PATCH 02/11] gnu: go-golang-org-x-net: Update to 0.5.0 Felix Lechner via Guix-patches via
2023-03-05 20:54 ` [bug#61989] [PATCH 03/11] gnu: Add go-github-com-hanwen-go-fuse-v2 Felix Lechner via Guix-patches via
2023-03-05 20:54 ` [bug#61989] [PATCH 04/11] gnu: Add go-github-com-aperturerobotics-jacobsa-crypto Felix Lechner via Guix-patches via
2023-03-05 20:54 ` [bug#61989] [PATCH 05/11] gnu: Add go-github-com-jacobsa-oglematchers Felix Lechner via Guix-patches via
2023-03-05 20:54 ` [bug#61989] [PATCH 06/11] gnu: Add go-github-com-jacobsa-oglemock Felix Lechner via Guix-patches via
2023-03-05 20:54 ` [bug#61989] [PATCH 07/11] gnu: Add go-github-com-jacobsa-ogletest Felix Lechner via Guix-patches via
2023-03-05 20:54 ` [bug#61989] [PATCH 08/11] gnu: Add go-github-com-jacobsa-reqtrace Felix Lechner via Guix-patches via
2023-03-05 20:54 ` [bug#61989] [PATCH 09/11] gnu: Add go-github-com-pkg-xattr Felix Lechner via Guix-patches via
2023-03-05 20:54 ` [bug#61989] [PATCH 10/11] gnu: Add go-github-com-rfjakob-eme Felix Lechner via Guix-patches via
2023-03-05 20:54 ` [bug#61989] [PATCH 11/11] gnu: Add gocryptfs Felix Lechner via Guix-patches via
2023-03-06 16:42 ` [bug#61989] [PATCH 00/11] Adding Gocryptfs (feature branch) Leo Famulari
2023-03-07 23:06   ` Leo Famulari
2023-03-08  0:02     ` Felix Lechner via Guix-patches via
2023-03-08 15:10       ` Leo Famulari
2023-03-10  0:21         ` Felix Lechner via Guix-patches via
2023-03-10  1:54           ` Leo Famulari
2023-03-11 16:17             ` Leo Famulari
2023-03-12  5:27               ` Felix Lechner via Guix-patches via
2023-03-14  2:05               ` Felix Lechner via Guix-patches via
2023-03-16  1:21                 ` Leo Famulari
2023-03-16 19:44                   ` Felix Lechner via Guix-patches via
2023-03-16 23:59                     ` Leo Famulari
2023-03-17 19:02                       ` Felix Lechner via Guix-patches via
2023-03-19  8:51                         ` Efraim Flashner [this message]
2023-03-19 17:17                           ` Leo Famulari
2023-03-19 17:22                             ` Leo Famulari
2023-03-19 17:25                               ` Felix Lechner via Guix-patches via
2023-03-19 20:38                                 ` Leo Famulari
2023-03-19 20:46                                   ` Leo Famulari
2023-03-19 20:48                                     ` Felix Lechner via Guix-patches via
2023-03-19 20:51                                       ` Leo Famulari
2023-03-19 20:54                                         ` Felix Lechner via Guix-patches via
2023-03-19 21:04                                           ` Leo Famulari
2023-03-19 21:31                                     ` Felix Lechner via Guix-patches via
2023-03-28 20:37                                       ` bug#61989: " Leo Famulari
2023-03-28 20:54                                         ` [bug#61989] " Felix Lechner via Guix-patches via
2023-03-13 17:53             ` Leo Famulari
2023-03-13 20:37               ` Felix Lechner via Guix-patches via

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=ZBbNJ5+Hp6ekQ3pH@3900XT \
    --to=efraim@flashner.co.il \
    --cc=61989@debbugs.gnu.org \
    --cc=felix.lechner@lease-up.com \
    --cc=leo@famulari.name \
    /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.