15424 2024-03-07 10:42:17 +0000 Can use fragments with no defaults if previous build had defconfig 2026-08-22 16:52:21 +0000 1 1 7 Build System, Metadata & Runtime OE-Core kernel 4.3 x86 Multiple ACCEPTED Medium+ normal 6.1 M3 1 ross.burton bruce.ashfield anis.bougrine10 randy.macleod richard.purdie tim.orling --- --- No (bug/feature does not impact docs) oldest_to_newest 98396 0 ross.burton 2024-03-07 10:42:17 +0000 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. 98401 1 bruce.ashfield 2024-03-07 14:07:10 +0000 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 ? 101750 2 randy.macleod 2025-04-24 18:54:46 +0000 Bulk move as requesting during YP BB meeting. 106613 3 anis.bougrine10 2026-08-22 16:52:21 +0000 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 ?