From: <changqing.li@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: [PATCH] go: fix multilib file conflicts
Date: Mon, 22 Dec 2025 11:24:55 +0800 [thread overview]
Message-ID: <20251222032455.2683666-1-changqing.li@windriver.com> (raw)
From: Changqing Li <changqing.li@windriver.com>
This is for fixing the following error of 'bitbake meta-go-toolchain'
when multilib is enabled:
Error: Transaction test error:
file /usr/bin/go conflicts between attempted installs of go-1.25.4-r0.x86_64_v3 and lib32-go-1.25.4-r0.core2_32
file /usr/bin/gofmt conflicts between attempted installs of go-1.25.4-r0.x86_64_v3 and lib32-go-1.25.4-r0.core2_32
Signed-off-by: Changqing Li <changqing.li@windriver.com>
---
meta/recipes-devtools/go/go_1.25.4.bb | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/meta/recipes-devtools/go/go_1.25.4.bb b/meta/recipes-devtools/go/go_1.25.4.bb
index 46f5fbc6be..372aa9538c 100644
--- a/meta/recipes-devtools/go/go_1.25.4.bb
+++ b/meta/recipes-devtools/go/go_1.25.4.bb
@@ -1,7 +1,7 @@
require go-${PV}.inc
require go-target.inc
-inherit linuxloader
+inherit linuxloader multilib_script
CGO_LDFLAGS:append = " -no-pie"
@@ -9,6 +9,8 @@ export GO_LDSO = "${@get_linuxloader(d)}"
export CC_FOR_TARGET = "gcc"
export CXX_FOR_TARGET = "g++"
+MULTILIB_SCRIPTS = "${PN}:${bindir}/go ${PN}:${bindir}/gofmt"
+
# mips/rv64 doesn't support -buildmode=pie, so skip the QA checking for mips/riscv32 and its
# variants.
python() {
--
2.34.1
next reply other threads:[~2025-12-22 3:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-22 3:24 changqing.li [this message]
2026-01-05 18:08 ` [OE-core] [PATCH] go: fix multilib file conflicts Ross Burton
2026-01-06 1:15 ` Changqing Li
2026-01-08 10:10 ` Ross Burton
2026-01-12 4:52 ` Changqing Li
[not found] ` <1889E2B366748363.2902090@lists.openembedded.org>
2026-01-21 2:00 ` Changqing Li
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=20251222032455.2683666-1-changqing.li@windriver.com \
--to=changqing.li@windriver.com \
--cc=openembedded-core@lists.openembedded.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox