On 6 Jan 2026, at 01:15, Changqing Li via lists.openembedded.org 
<[email protected]> 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 
>> <[email protected]> wrote:
>> 
>>> From: Changqing Li <[email protected]>
>>> 
>>> 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?

Ross
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#229053): 
https://lists.openembedded.org/g/openembedded-core/message/229053
Mute This Topic: https://lists.openembedded.org/mt/116896974/21656
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to