From: Marcel van der Boom <marcel@van-der-boom.nl>
To: Jack Hill <jackhill@jackhill.us>
Cc: "John Kehayias" <john.kehayias@protonmail.com>,
68212@debbugs.gnu.org, "Ludovic Courtès" <ludo@gnu.org>,
"Efraim Flashner" <efraim@flashner.co.il>
Subject: [bug#68212] [PATCH v2] gnu: openssh: fix build on ppc64le.
Date: Thu, 18 Jan 2024 10:22:10 +0100 [thread overview]
Message-ID: <874jfb9et9.fsf@van-der-boom.nl> (raw)
In-Reply-To: <f9de675e-4fc4-c48f-9ae1-7a4c0288daca@jackhill.us> (Jack Hill's message of "Wed, 17 Jan 2024 12:07:54 -0500 (EST)")
This still fails for me, and apparently also on the build farm:
https://ci.guix.gnu.org/build/3266550/details
if I am reading it properly that build is after the described
patch. The log has the same error as I have locally when building
openssh
Interestingly, since the openssh release I have this in my
manifest which *succeeds* in building openssh:
(define-public openssh-next
(let ((xcommit "1036d77b34a5fa15e56f516b81b9928006848cbd"))
(package
(inherit openssh)
(name "openssh-next")
(version "9.6p1-1")
(native-inputs
(list autoconf
automake
pkg-config))
(source
(origin
(method git-fetch)
(uri (git-reference
(url
"https://github.com/openssh/openssh-portable.git")
(commit xcommit)))
(file-name (git-file-name name version))
(patches (search-patches
"openssh-trust-guix-store-directory.patch"))
(sha256
(base32
"1sary1ig972l4zjvpzncf9whfp5ab8snff2fw9sy5a8pda5n2a7w")))))))
This just refers to the commit that holds the patch, so in theory
it should be the same as the applied patch, no?
Am I overlooking something?
[Jack Hill]:
> This was applied to master by Ludo’ in
> ef270f9d73203c1b19c6163ce4d4257a52bfb605
> Thanks and closing!
> Best,
> Jack
--
Marcel van der Boom → marcel@van-der-boom.nl
prev parent reply other threads:[~2024-01-18 9:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-02 16:53 [bug#68212] [PATCH] gnu: openssh: fix build one ppc64le Jack Hill
2024-01-02 16:54 ` [bug#68212] [PATCH v2] gnu: openssh: fix build on ppc64le Jack Hill
2024-01-17 17:07 ` bug#68212: " Jack Hill
2024-01-18 9:22 ` Marcel van der Boom [this message]
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=874jfb9et9.fsf@van-der-boom.nl \
--to=marcel@van-der-boom.nl \
--cc=68212@debbugs.gnu.org \
--cc=efraim@flashner.co.il \
--cc=jackhill@jackhill.us \
--cc=john.kehayias@protonmail.com \
--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.