From: ChenQi <Qi.Chen@windriver.com>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: bitbake-devel@lists.openembedded.org, richard.purdie@linuxfoundation.org
Subject: Re: [bitbake-devel][PATCH V2] lib/bb/parse/ast.py: error out for internal fragment in case of a previous value
Date: Fri, 14 Nov 2025 15:17:19 +0800 [thread overview]
Message-ID: <afddd5c5-ab6b-4e9a-a667-93408a2d070c@windriver.com> (raw)
In-Reply-To: <451e3958-7661-4070-bff9-b3bce661c21d@windriver.com>
On 11/14/25 15:12, Chen Qi via lists.openembedded.org wrote:
> 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
>
Hi Alex,
Ignore the reply below. Sorry, I just realized what's going on here.
I was using 'MACHINE ="qemuarm64"' in local.conf to test things.
So the error will appear again and again even with a simple
'bitbake-config-build --help' if there's no such special exception.
Regards,
Qi
> 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
>
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#18387): https://lists.openembedded.org/g/bitbake-devel/message/18387
> Mute This Topic: https://lists.openembedded.org/mt/116288219/7304865
> Group Owner: bitbake-devel+owner@lists.openembedded.org
> Unsubscribe: https://lists.openembedded.org/g/bitbake-devel/unsub [Qi.Chen@eng.windriver.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
next prev parent reply other threads:[~2025-11-14 7:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-14 6:02 [bitbake-devel][PATCH V2] lib/bb/parse/ast.py: error out for internal fragment in case of a previous value Qi.Chen
2025-11-14 6:15 ` Alexander Kanavin
2025-11-14 6:20 ` ChenQi
2025-11-14 6:28 ` Alexander Kanavin
2025-11-14 6:37 ` ChenQi
2025-11-14 6:49 ` Alexander Kanavin
2025-11-14 7:12 ` ChenQi
2025-11-14 7:17 ` ChenQi [this message]
2025-11-14 11:50 ` Alexander Kanavin
2025-11-14 12:14 ` Richard Purdie
[not found] ` <1877DE8BA2A633E6.930811@lists.openembedded.org>
2025-11-14 12:17 ` Richard Purdie
2025-11-17 2:37 ` ChenQi
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=afddd5c5-ab6b-4e9a-a667-93408a2d070c@windriver.com \
--to=qi.chen@windriver.com \
--cc=alex.kanavin@gmail.com \
--cc=bitbake-devel@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.