On 07/01/2014 19:11, Hart, Darren wrote: > > Please check for the functionality, not KERNEL_VERSION. The > KERNEL_VERSION doesn't allow for backports and such which might add this > ability. Grep the Makefile for the target, for example, if the above OR > statement isn't adequate. >
I guess the OR is perfectly fine then. For whatever reason make oldnoconfig fails, we'll fall back to the old behavior. > As Bruce stated, it seems that the fix would be to use the updated > Kconfig, not default to setting things to NO. The problem with that > approach is it doesn't accept defaults for non-specified options (which > when updating kernel versions, is often the preferred approach). > I think you got it wrong: - I am already using an updated kconfig (I even backported it on the older kernel version) - make oldnoconfig is NOT setting things to NO but to the default value of the unspecified options (exactly what we need). The choice of the name was not wise and It has been renamed olddefconfig since 3.7 -- Alexandre Belloni, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
