From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Christian Stewart <christian@paral.in>
Cc: Anisse Astier <anisse@astier.eu>,
"Yann E . MORIN" <yann.morin.1998@free.fr>,
Christian Stewart via buildroot <buildroot@buildroot.org>
Subject: Re: [Buildroot] [PATCH 1/1] package/gocryptfs: fix build against riscv
Date: Mon, 25 Jul 2022 08:42:25 +0200 [thread overview]
Message-ID: <20220725084225.40a20846@windsurf> (raw)
In-Reply-To: <CA+h8R2rcc=sqTDY0HtE4UNUJydVZFd16PWXLXGaHo+wK0aVN6Q@mail.gmail.com>
On Sun, 24 Jul 2022 23:27:46 -0700
Christian Stewart <christian@paral.in> wrote:
> I don't think it's that the fork changed the deps, rather that the
> newer version of Go (1.18) drops those lines whereas a previous
> version would have kept them.
Ah, ok, makes more sense to me, thanks for the explanation.
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-07-25 6:42 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 [this message]
2022-08-02 22:06 ` Thomas Petazzoni via buildroot
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=20220725084225.40a20846@windsurf \
--to=buildroot@buildroot.org \
--cc=anisse@astier.eu \
--cc=christian@paral.in \
--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 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.