From: aoiblue775@gmail.com
To: meta-freescale@lists.yoctoproject.org
Subject: Updating from Warrior to Kirkstone bitbake failure #imx8qxp #kirkstone #meta-freescale #yocto
Date: Wed, 20 Dec 2023 11:19:00 -0800 [thread overview]
Message-ID: <fypm.1703099940655866705.CRGc@lists.yoctoproject.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 4011 bytes --]
Hello,
This is my first post on this email forum, please understand that I may not know what I'm doing or how things work around here.
I'm updating a project that was initially a warrior branch of Yocto, I've gotten past all the conf updating steps (changing _ to : and so on...). I'm on the last step, at least, I hope it's the last step (getting Bitbake to compile).
Below is the snippet of the console when I try compiling. I'm not really sure how to go about fixing this, I've tried grep-ing for files that contain tune-cortexa53-crypto (nothing). I've tried a different version of the poky warrior branch revision code, no change.
I'm just starting my career in Yocto, so any help/tips would be greatly appreciated.
Please note some things in the terminal output snippet below may have been redacted for security purposes.
# bitbake image
bitbake image-project-devroot:do_build cst-native:do_build project-old:do_compile
ERROR: OE-core's config sanity checker detected a potential misconfiguration.
Either fix the cause of this error or at your own risk disable the checker (see sanity.conf).
Following is the list of potential problems / advisories:
Error, the PACKAGE_ARCHS variable (all any noarch ${PACKAGE_EXTRA_ARCHS:tune-cortexa53-crypto} internal_som) for DEFAULTTUNE (cortexa53-crypto) does not contain TUNE_PKGARCH (${@bb.utils.con
tains('TUNE_FEATURES', 'aarch64', '${ARMPKGARCH:tune-cortexa53-crypto}', '${ARMPKGARCH:tune-cortexa53-crypto}', d)}).Toolchain tunings invalid:
Tuning 'cortexa53-crypto' has no defined features, and cannot be used.
You are building in a path included in PSEUDO_IGNORE_PATHS /home/builder/repos/yocto-update-test/maybe-trunk/build/build/tmp/work/${@bb.utils.contains('TUNE_FEATURES' please locate the build
outside this path.
You are building in a path included in PSEUDO_IGNORE_PATHS /home/builder/repos/yocto-update-test/maybe-trunk/build/build/tmp/work/${@bb.utils.contains('TUNE_FEATURES' please locate the build
outside this path.
You are building in a path included in PSEUDO_IGNORE_PATHS /home/builder/repos/yocto-update-test/maybe-trunk/build/build/tmp/work/${@bb.utils.contains('TUNE_FEATURES' please locate the build
outside this path.
You are building in a path included in PSEUDO_IGNORE_PATHS /home/builder/repos/yocto-update-test/maybe-trunk/build/build/tmp/work/${@bb.utils.contains('TUNE_FEATURES' please locate the build
outside this path.
You are building in a path included in PSEUDO_IGNORE_PATHS /home/builder/repos/yocto-update-test/maybe-trunk/build/build/tmp/work/${@bb.utils.contains('TUNE_FEATURES' please locate the build
outside this path.
You are building in a path included in PSEUDO_IGNORE_PATHS /home/builder/repos/yocto-update-test/maybe-trunk/build/build/tmp/work/${@bb.utils.contains('TUNE_FEATURES' please locate the build
outside this path.
A path included in PSEUDO_IGNORE_PATHS /home/builder/repos/yocto-update-test/maybe-trunk/build/build/tmp/work/${@bb.utils.contains('TUNE_FEATURES' and the path /home/builder/repos/yocto-upda
te-test/maybe-trunk/build/build/tmp/work/${@bb.utils.contains('TUNE_FEATURES' overlap and this will break pseudo permission and ownership tracking. Please set the path /home/builder/repos/yoc
to-update-test/maybe-trunk/build/build/tmp/work/${@bb.utils.contains('TUNE_FEATURES' to a different directory which does not overlap with pseudo controlled directories.
A path included in PSEUDO_IGNORE_PATHS /home/builder/repos/yocto-update-test/maybe-trunk/build/build/tmp/work/${@bb.utils.contains('TUNE_FEATURES' and the path /home/builder/repos/yocto-upda
te-test/maybe-trunk/build/build/tmp/work/${@bb.utils.contains('TUNE_FEATURES' overlap and this will break pseudo permission and ownership tracking. Please set the path /home/builder/repos/yoc
to-update-test/maybe-trunk/build/build/tmp/work/${@bb.utils.contains('TUNE_FEATURES' to a different directory which does not overlap with pseudo controlled directories.
Thank you for your time.
[-- Attachment #2: Type: text/html, Size: 4095 bytes --]
next reply other threads:[~2023-12-20 19:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-20 19:19 aoiblue775 [this message]
2023-12-21 21:27 ` Updating from Warrior to Kirkstone bitbake failure #imx8qxp #kirkstone #meta-freescale #yocto aoiblue775
2024-02-29 17:17 ` [meta-freescale] " Daiane Angolini
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=fypm.1703099940655866705.CRGc@lists.yoctoproject.org \
--to=aoiblue775@gmail.com \
--cc=meta-freescale@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).