From: Changqing Li <changqing.li@windriver.com>
To: Ross Burton <Ross.Burton@arm.com>
Cc: "openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>,
Khem Raj <raj.khem@gmail.com>,
Alexander Kanavin <alex.kanavin@gmail.com>
Subject: Re: [OE-core] [PATCH] go: fix multilib file conflicts
Date: Mon, 12 Jan 2026 12:52:55 +0800 [thread overview]
Message-ID: <e07e5e63-5484-4331-8a4a-6eb4027c1a38@windriver.com> (raw)
In-Reply-To: <D3892BD1-671E-4177-9154-08CA89880ADC@arm.com>
On 1/8/26 18:10, Ross Burton wrote:
> CAUTION: This email comes from a non Wind River email account!
> Do not click links or open attachments unless you recognize the sender and know the content is safe.
>
> On 6 Jan 2026, at 01:15, Changqing Li via lists.openembedded.org <changqing.li=windriver.com@lists.openembedded.org> wrote:
>>
>> On 1/6/26 02:08, Ross Burton wrote:
>>> CAUTION: This email comes from a non Wind River email account!
>>> Do not click links or open attachments unless you recognize the sender and know the content is safe.
>>>
>>> On 22 Dec 2025, at 03:24, Changqing Li via lists.openembedded.org <changqing.li=windriver.com@lists.openembedded.org> wrote:
>>>
>>>> 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
>>>>
>>> Why would you do this though? We don’t support installing bash and lib32-bash either.
>> Hi, Ross
>> The issue reproduced when multilib is enabled globally in local.conf by following config:
>> ```
>> require conf/multilib.conf
>> MULTILIBS ?= "multilib:lib32"
>> DEFAULTTUNE:virtclass-multilib-lib32 ?= "core2-32"
>> ```
>> bitbake meta-go-toolchain will failed with above failure.
>>
>> [snip of meta-go-toolchain.bb]
>> TOOLCHAIN_TARGET_TASK:append = " \ ${@multilib_pkg_extend(d, 'packagegroup-go-sdk-target')} \ "
>> [snip of meta-go-toolchain.bb]
>>
>> go is in packagegroup-go-sdk-target, it is extended by multilib_pkg_extend. so both go and lib32-go will be installed.
>> go is added in to packagegroup-go-sdk-target for providing entire toolchain include compiler.
> Maybe the packagegroup shouldn’t be doing that expansion then?
We don't want go to be extended, but packagegroup-go-sdk-target not only include go, it also includes go-runtime/go-runtime-dev, we need to extend go-runtime/go-runtime-dev.
so fix go packaging for multilib as this patch to avoid the conflicts issue.
//Changqing
>
> Ross
next prev parent reply other threads:[~2026-01-12 4:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-22 3:24 [PATCH] go: fix multilib file conflicts changqing.li
2026-01-05 18:08 ` [OE-core] " Ross Burton
2026-01-06 1:15 ` Changqing Li
2026-01-08 10:10 ` Ross Burton
2026-01-12 4:52 ` Changqing Li [this message]
[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=e07e5e63-5484-4331-8a4a-6eb4027c1a38@windriver.com \
--to=changqing.li@windriver.com \
--cc=Ross.Burton@arm.com \
--cc=alex.kanavin@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@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