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 14:37:40 +0800 [thread overview]
Message-ID: <5fffd119-5b6c-462d-9f1e-5b2b30f81715@windriver.com> (raw)
In-Reply-To: <CANNYZj8tDk8izGO2f_8ADHsaN9VudG_hsQrcw2N2O8NnXtdCCQ@mail.gmail.com>
On 11/14/25 14:28, Alexander Kanavin wrote:
> On Fri, 14 Nov 2025 at 07:20, ChenQi <Qi.Chen@windriver.com> wrote:
>> I know that the env method is a horrible hack. I looked around but could not find any other choice. Do you have any suggestion?
> I don't understand why the special exception in bitbake-config-build
> is needed to begin with. What is the scenario where it is necessary?
>
> Alex
Let me use an example to explain this one.
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.
Regards,
Qi
next prev parent reply other threads:[~2025-11-14 6:37 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 [this message]
2025-11-14 6:49 ` Alexander Kanavin
2025-11-14 7:12 ` ChenQi
2025-11-14 7:17 ` ChenQi
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=5fffd119-5b6c-462d-9f1e-5b2b30f81715@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.