If I build a kernel with a defconfig in SRC_URI and no KCONFIG_MODE set then merge_config.sh is passed -n so that it does a 'default=no' build on the assumption that the defconfig is absolutely complete. If I then decide to use fragments but do not clean the kernel build, do_kernel_configme() will see the defconfig still remains in the work tree and pass -n to merge_config.sh still. This <cough> can result in much confusion as to why many kernel options that should be enabled by default are not when writing new fragments.
I can think of two ways to fix this off the top of my head: a) make sure that the defconfig in workdir is listed as something that needs to be cleaned b) if there's no in-tree defconfig specified and no defconfig in the SRC_URI that is found, ignore/delete on if located in WORKDIR. Any preferences ?
Bulk move as requesting during YP BB meeting.
If I am not mistaken, this issue has been resolved thanks to this commit https://git.openembedded.org/openembedded-core/commit/?h=master-next&id=86fec41b1e809d1a2fa2feadc26d29020df53d39 isn't it ?