Hi Bruce, I've been wondering why some kernels show up the source files issues and some don't.
In order for it to happen it seems we need CONFIG_DEBUG_INFO set. That appears to be set by default for beaglebone but not for qemux86-64. I wasn't sure where/how that is getting pulled into the BSPs, qemu or otherwise. It is more important now that create-spdx relies upon it. I know you can manually do it with something like: KERNEL_EXTRA_FEATURES:append = " features/debug/debug-kernel.scc" So just to be clear, to reproduce the kernel warnings I think you need a build which: a) has CONFIG_DEBUG_INFO set (e.g. beaglebone-yocto) b) has buildpaths in WARN_QA: https://git.yoctoproject.org/poky/commit/?h=master-next&id=8c5ac30a987c40c41df8a483f353a22fe487789e c) reverts the package.bbclass change: https://git.yoctoproject.org/poky/commit/?h=master-next&id=02b811eba6e28e940b1e219709c2be82ce047fbb d) doesn't build from existing sstate as you wouldn't get warnings shown so a "bitbake linux-yocto -C package_qa" at least based on my current understanding anyway. Cheers, Richard
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#168034): https://lists.openembedded.org/g/openembedded-core/message/168034 Mute This Topic: https://lists.openembedded.org/mt/92379610/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
