From: Michael Opdenacker <michael.opdenacker@rootcommit.com>
To: Gyorgy Sarvari <skandigraun@gmail.com>,
OE-core <openembedded-core@lists.openembedded.org>
Cc: michael.opdenacker@rootcommit.com, Khem Raj <raj.khem@gmail.com>
Subject: Re: [OE-core] linux-yocto.inc: remove riscv-isa-clear.scc from KERNEL_FEATURES_RISCV?
Date: Thu, 27 Nov 2025 11:03:14 +0000 (UTC) [thread overview]
Message-ID: <7e4c03b7-8f5c-4e92-91b2-1535e5533f8d@rootcommit.com> (raw)
In-Reply-To: <73131023-79db-445a-8341-0b455dd586f6@gmail.com>
Hi Gyorgy
On 11/27/25 11:46, Gyorgy Sarvari wrote:
>
> On 11/27/25 11:20, Michael Opdenacker via lists.openembedded.org wrote:
>> Greetings,
>>
>> I'm getting the same issue trying a master build on several RISC-V boards:
>>
>> ERROR: linux-milkv-duo-dev-1.0-r0 do_kernel_metadata: Feature
>> 'arch/riscv/tunes/riscv-isa-clear.scc' not found, this will cause
>> configuration failures.
>> ERROR: linux-milkv-duo-dev-1.0-r0 do_kernel_metadata: Check the SRC_URI
>> for meta-data repositories or directories that may be missing
>> ERROR: linux-milkv-duo-dev-1.0-r0 do_kernel_metadata: Set
>> KERNEL_DANGLING_FEATURES_WARN_ONLY to ignore this issue
>>
>> OK, I can set
>> KERNEL_DANGLING_FEATURES_WARN_ONLY = "1"
>> but is this a clean solution?
>>
>> Where are all the arch/riscv/tunes/riscv-isa-*.scc files supposed to be?
>> I didn't manage to find them anywhere...
> Do you have the yocto-kernel-cache[1] repo in your SRC_URI? The scc
> files come from there
>
> [1]: https://git.yoctoproject.org/yocto-kernel-cache/tree/arch/riscv/tunes
Ho, thanks! That was exactly what I needed.
I will add these to my kernel recipes.
Thanks again,
Cheers
Michael.
--
Michael Opdenacker
Root Commit
Yocto Project and OpenEmbedded Training course - Learn by doing:
https://rootcommit.com/training/yocto/
next prev parent reply other threads:[~2025-11-27 11:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-27 10:20 linux-yocto.inc: remove riscv-isa-clear.scc from KERNEL_FEATURES_RISCV? Michael Opdenacker
2025-11-27 10:46 ` [OE-core] " Gyorgy Sarvari
2025-11-27 11:03 ` Michael Opdenacker [this message]
2025-11-28 13:40 ` Michael Opdenacker
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=7e4c03b7-8f5c-4e92-91b2-1535e5533f8d@rootcommit.com \
--to=michael.opdenacker@rootcommit.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.com \
--cc=skandigraun@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox