The configuration was specified in the build using "-R": bitbake -R layers/meta-manufacturing/conf/iotr_rammfg.conf mlinux-iotr-rammfg-image
It is not obvious to me how an external kernel module will use INITRAMFS_IMAGE, but I am seeing this message when running diagnostics after an external kernel module build error: NOTE: Running task 2854 of 4859 (/home/jenkins/workspace/mlinux/iotr-iotrouter/layers/meta-multitech-nxp/recipes-kernel/mxm-wifiex/mxm-wifiex_5.15.71.bb:do_fetch) ERROR: When reparsing /home/jenkins/workspace/mlinux/iotr-iotrouter/layers/meta-multitech-nxp/recipes-kernel/mxm-wifiex/mxm-wifiex_5.15.71.bb:do_package_qa, the basehash value changed from ... bitbake mxm-wifiex -cdo_package_write_ipk -Sprintdiff output: Variable INITRAMFS_IMAGE value changed from 'mlinux-iotr-rammfg-image' to '' The only value I can see for INITRAMFS_IMAGE: iotr_rammfg.conf:INITRAMFS_IMAGE = "mlinux-iotr-rammfg-image" Despite the errors and a bitbake failure status, the IPK files for this kernel module are created successfully, and the image is also created. Is there a way to exclude INITRAMFS_IMAGE from being considered when building my external kernel module? This is from Kirkstone: 2022-04.14 John Klug
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#61999): https://lists.yoctoproject.org/g/yocto/message/61999 Mute This Topic: https://lists.yoctoproject.org/mt/103283055/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
