Re: [bitbake-devel][PATCH V2] lib/bb/parse/ast.py: error out for internal fragment in case of a previous value

[ChenQi <Qi.Chen@windriver.com>]

On 11/14/25 14:49, Alexander Kanavin wrote:
> On Fri, 14 Nov 2025 at 07:37, ChenQi <Qi.Chen@windriver.com> wrote:
>> When machine/qemux86-64 fragment is enabled and users use 'MACHINE=xxx
>> bitbake <pkg>', the expected behavior is to error out and recommend user
>> to use 'bitbake-config-build disable-fragment'.
>>
>> Here comes the problem. bitbake-config-build makes use of tinfoil and
>> when setting up tinfoil, the above error will appear again. We can't
>> recommend users to use 'bitbake-config-build disable-fragment' while the
>> recommended method still errors out. This is the reason for the special
>> exception.
> But why would users be running 'MACHINE=xxx bitbake-config-build
> disable-fragment ...' ? That prefix is intended only for bitbake
> invocations.
>
> Alex

I mean that users run something like 'MACHINE=qemuarm64 bitbake 
base-files', and they get error like below:

ERROR: A builtin fragment 'machine/qemux86-64' is used while MACHINE has 
already got an assignment.
Please either disable the fragment or remove the value assignment.
To disable the fragment, use 'bitbake-config-build disable-fragment 
machine/qemux86-64'.

Now they run 'bitbake-config-build disable-fragment machine/qemux86-64' 
as recommended. If there's no such special exception, they will get the 
same error again. Even if they run a simple 'bitbake-config-build 
--help', they'll get the same error again.

That's the reason for this special exception.

Regards,
Qi