From: WANG Xuerui <xen0n@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: WANG Xuerui <xen0n@gentoo.org>,
Thilo Fromm <thilo.alexander@gmail.com>,
Flatcar Linux Maintainers <infra@flatcar-linux.org>
Subject: [gentoo-dev] [PATCH 0/2] go-env.eclass: niche platform fixes
Date: Thu, 23 Nov 2023 17:31:57 +0800 [thread overview]
Message-ID: <20231123093159.1228864-1-xen0n@gentoo.org> (raw)
Hi,
Here are some fixes to the recently added go-env.eclass that broke Go
ebuilds on several arches (loong and riscv confirmed). I've tested on
loong to confirm.
You can also view this series on GitHub [1], should you prefer that.
[1]: https://github.com/gentoo/gentoo/pull/33941
WANG Xuerui (2):
go-env.eclass: unify GOARCH mapping logic with dev-lang/go
go-env.eclass: also set GOARM & GO386 when applicable
eclass/go-env.eclass | 61 ++++++++++++++++++++++++++++++++++----------
1 file changed, 47 insertions(+), 14 deletions(-)
--
2.42.1
next reply other threads:[~2023-11-23 9:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-23 9:31 WANG Xuerui [this message]
2023-11-23 9:31 ` [gentoo-dev] [PATCH 1/2] go-env.eclass: unify GOARCH mapping logic with dev-lang/go WANG Xuerui
2023-11-23 9:31 ` [gentoo-dev] [PATCH 2/2] go-env.eclass: also set GOARM & GO386 when applicable WANG Xuerui
2023-11-23 23:01 ` Ionen Wolkens
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=20231123093159.1228864-1-xen0n@gentoo.org \
--to=xen0n@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=infra@flatcar-linux.org \
--cc=thilo.alexander@gmail.com \
/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