5574 2013-11-20 11:56:41 +0000 Add kernel configuration check mechanism 2026-07-09 15:50:58 +0000 1 1 7 Build System, Metadata & Runtime OE-Core core 1.6 All Multiple NEW Low enhancement Future 1 bluelightning unassigned akuster dmitriy.korovkin dvhart meta.mr.watcher meta.watcher otavio paulg randy.macleod winfried_mb2 --- --- Yes (doc changes required) oldest_to_newest 38924 0 bluelightning 2013-11-20 11:56:41 +0000 Some recipes build software that needs a particular version of the kernel (or newer) or particular kernel configuration options enabled; good examples are systemd and udev. It would be nice if the build system could allow the recipe to specify these requirements and then we could check and report a sensible error if they are not satisfied; currently you can omit important options from the kernel configuration and the result will be a non-booting image, often with no clear indicator as to what went wrong. 38996 1 dvhart 2013-11-21 15:50:06 +0000 Version testing is very seriously discouraged by folks like Greg KH, encouraging people instead to be testing for particular features. Can we do this via CONFIG_* testing instead? 38997 2 dvhart 2013-11-21 15:51:06 +0000 This is especially important for things like LTSI kernels where features from future kernels can be backported and the version test would return false failures. 53960 3 winfried_mb2 2015-09-11 09:35:27 +0000 I think this is an important feature to have. I just spent two days trying to figure out why systemd didn't work properly. In the end it was a missing CONFIG_FHANDLE. 56372 4 bluelightning 2015-11-10 19:31:36 +0000 FWIW what Darren says above makes sense, we ought to be looking at the configuration not the version; I've modified the title to match. Another important place we should be checking this just occurred to me today - IMAGE_FSTYPES; it's no good building a kernel with btrfs disabled at the same time as you build an image that you're going to use as your root filesystem and formatting it as btrfs. Hopefully we should be able to add a check for that using this same mechanism (or at least part of it). 66169 5 bluelightning 2016-09-14 23:50:53 +0000 Bruce was strongly against this when I proposed it as an RFC: https://patchwork.openembedded.org/patch/121933/ I'll re-evaluate what's been done in the recent kernel config handling changes during the 2.3 timeframe and work out how to proceed. 77558 6 akuster 2017-10-12 23:30:17 +0000 some input. The use case I have is for qa tests that are in the meta-qa layer. If I add the automount test for example, it has kernel config dependences for ext2/3/4 and more. It would be nice to have a "WARN" at compile time if the kernel configs this test needs are not set or provide a method to set them. I am aware of KERNEL_FEATURES_append but that seems to only work with yocto-kernel-cache, it would be nice to extend this beyond the yocto kernels. ( yes a separate discussion) 106149 7 randy.macleod 2026-07-09 15:50:58 +0000 Dmitriy, A 'future' enhancement that you may be interested in later this year.