From: Felix Mellmann <flix.yocto@benfm.de>
To: yocto@lists.yoctoproject.org
Subject: icecc support broken?
Date: Sat, 30 Dec 2023 10:31:29 +0100 [thread overview]
Message-ID: <d7fa009c81cdef2d821fd879c44619a4@benfm.de> (raw)
Hi,
to speed up the build process I would like to use icecc as described in
the manual (https://docs.yoctoproject.org/singleindex.html#icecc). When
using Yocto 4.3.1 this leads to an error while parsing the recipes:
ERROR: /Yocto/poky/meta/recipes-core/meta/target-sdk-provides-dummy.bb:
no-pn NULL prefix
WARNING:
/Yocto/poky/meta/recipes-core/meta/target-sdk-provides-dummy.bb:
Exception during build_dependencies for set_icecc_env
WARNING:
/Yocto/poky/meta/recipes-core/meta/target-sdk-provides-dummy.bb: Error
during finalise of
/Yocto/poky/meta/recipes-core/meta/target-sdk-provides-dummy.bb
I bisected this problem down to poky commit 3be00a (bitbake.conf: Add
BB_HASH_CODEPARSER_VALS). Since then the problem seem to exist.
And voila when I remove "PN=no-pn" from BB_HASH_CODEPARSER_VALS in
bitbake.conf or add
BB_HASH_CODEPARSER_VALS:remove = "PN=no-pn"
to my local.conf the recipes get parsed again and the build starts.
Currently I'm building a vanilla yocto-4.3.1 core-image-full-cmdline for
qemu using icecc and see if other problems are arising.
Actually I'm not able to tell what BB_HASH_CODEPARSER_VALS does and
what's the outcome of removing this entry. But this issue shall be
either fixed or documented within the manual.
Is icecc and the support within oe/yocto still actively maintained or is
there any superior mechanism I'm not yet aware of?
Best regards,
Felix
next reply other threads:[~2023-12-30 9:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-30 9:31 Felix Mellmann [this message]
2023-12-30 16:56 ` [yocto] icecc support broken? Alexander Kanavin
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=d7fa009c81cdef2d821fd879c44619a4@benfm.de \
--to=flix.yocto@benfm.de \
--cc=yocto@lists.yoctoproject.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox