From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: peter.suti@streamunlimited.com, openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH 1/1] icecc: calculate pn and bpn from FILE
Date: Tue, 03 Jun 2025 10:40:32 +0100 [thread overview]
Message-ID: <b535bfb0baaa86f325ff88e21b8bf3a8378b4635.camel@linuxfoundation.org> (raw)
In-Reply-To: <20250603085808.4045687-1-peter.suti@streamunlimited.com>
On Tue, 2025-06-03 at 10:58 +0200, Peter Suti via lists.openembedded.org wrote:
> Starting with Yocto Mickledore the PN and BPN variables are set to "no-pn"
> at this point in the `use_icecc()` function, so instead we need to
> re-parse them from the file again as a workaround otherwise icecc is broken.
>
> Fixes: 3be00ad9052de ("bitbake.conf: Add BB_HASH_CODEPARSER_VALS")
> Where "PN=nopn" is set to optimise the codeparser cache's size.
>
> [0] https://lists.yoctoproject.org/g/yocto/topic/icecc_support_broken/103429714
>
> Signed-off-by: Peter Suti <peter.suti@streamunlimited.com>
> ---
> meta/classes/icecc.bbclass | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/meta/classes/icecc.bbclass b/meta/classes/icecc.bbclass
> index 8a48f2ad63..e3b07028b8 100644
> --- a/meta/classes/icecc.bbclass
> +++ b/meta/classes/icecc.bbclass
> @@ -143,8 +143,8 @@ def use_icecc(bb,d):
> if icecc_is_cross_canadian(bb, d):
> return "no"
>
> - pn = d.getVar('PN')
> - bpn = d.getVar('BPN')
> + pn = bb.parse.vars_from_file(d.getVar('FILE', False),d)[0] or 'defaultpkgname'
> + bpn = oe.utils.prune_suffix(pn, d.getVar('SPECIAL_PKGSUFFIX').split(), d)
>
> # Enable/disable checks are made against BPN, because there is a good
> # chance that if icecc should be skipped for a recipe, it should be skipped
Unfortunately PN could be set differently to that, or set through class
extensions so I don't think this is a good way to fix the issue. It
does highlight that icecc probably just worked through luck anyway. It
would get it approximately right most of the time but I'm not sure we
want to rely on that.
To be honest, I'm more tempted to simply remove icecc since it would
seem not a lot of people are using it if it takes this long for fixes
to get sent :/.
Cheers,
Richard
next prev parent reply other threads:[~2025-06-03 9:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-03 8:58 [PATCH 1/1] icecc: calculate pn and bpn from FILE Peter Suti
2025-06-03 9:40 ` Richard Purdie [this message]
[not found] ` <18457EF875184E76.9693@lists.openembedded.org>
2025-06-03 9:58 ` [OE-core] " Richard Purdie
2025-06-03 11:01 ` Peter Suti
2025-06-03 21:55 ` Douglas Royds
2025-06-03 22:15 ` Richard Purdie
2025-06-03 23:23 ` Joshua Watt
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=b535bfb0baaa86f325ff88e21b8bf3a8378b4635.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=peter.suti@streamunlimited.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 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.