From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Christian Stewart via buildroot <buildroot@buildroot.org>
Cc: "Yann E . MORIN" <yann.morin.1998@free.fr>,
Anisse Astier <anisse@astier.eu>
Subject: Re: [Buildroot] [PATCH 1/1] package/gocryptfs: fix build against riscv
Date: Wed, 3 Aug 2022 00:06:27 +0200 [thread overview]
Message-ID: <20220803000627.74f6a12f@windsurf> (raw)
In-Reply-To: <20220625224224.1446787-1-christian@paral.in>
On Sat, 25 Jun 2022 15:42:24 -0700
Christian Stewart via buildroot <buildroot@buildroot.org> wrote:
> Replace dependency jacobsa/crypto with a fork with support for riscv64.
>
> Fixes:
> - http://autobuild.buildroot.net/results/caa60874781c4077273884eb37281cc9e02ef9ac/
> - https://github.com/rfjakob/gocryptfs/issues/666
>
> Upstream PR: https://github.com/jacobsa/crypto/issues/13
>
> Signed-off-by: Christian Stewart <christian@paral.in>
> ---
> ...-fix-jacobsa-crypto-build-on-riscv64.patch | 152 ++++++++++++++++++
> 1 file changed, 152 insertions(+)
> create mode 100644 package/gocryptfs/0001-go.mod-fix-jacobsa-crypto-build-on-riscv64.patch
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-08-02 22:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-25 22:42 [Buildroot] [PATCH 1/1] package/gocryptfs: fix build against riscv Christian Stewart via buildroot
2022-07-23 16:41 ` Thomas Petazzoni via buildroot
2022-07-23 19:44 ` Christian Stewart via buildroot
2022-07-23 20:22 ` Thomas Petazzoni via buildroot
2022-07-24 23:42 ` Christian Stewart via buildroot
2022-07-25 6:25 ` Thomas Petazzoni via buildroot
2022-07-25 6:27 ` Christian Stewart via buildroot
2022-07-25 6:42 ` Thomas Petazzoni via buildroot
2022-08-02 22:06 ` Thomas Petazzoni via buildroot [this message]
2022-09-14 9:10 ` Peter Korsgaard
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=20220803000627.74f6a12f@windsurf \
--to=buildroot@buildroot.org \
--cc=anisse@astier.eu \
--cc=thomas.petazzoni@bootlin.com \
--cc=yann.morin.1998@free.fr \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox