On 16/07/16 14:35, Baptiste Jonglez wrote:
Hi,
On Fri, Jul 15, 2016 at 09:07:07AM +0100, David Fernandez wrote:
I'm trying to have a kernel package to emnable some kernel configuration
settings.
I've tried using the KCONFIG:=CONFIG_XXX in the kernel packages, or creating
"config KERNEL_XXX" in any kind of package.
Only to find that the setting makes it as far as $(LINUX_DIR)/.config.set
but never into $(LINUX_DIR)/.config
Is there a way to do this?
There is a strange bug with Kconfig, maybe you are hitting it. Basically,
if a Kconfig symbol does not have a string description attached to it, it
is not possible to select it directly.
I've realized of that when trying to select it usinf kernel_menuconfig.
Seems that some kernel packages select them indirectly using:
config XXX
triestate "My awesome configuration setting."
...
select YYY
...
when:
config YYY
bool
...
Have a look at all the "kconfig hacks" patches that are here as
workaround, for instance:
https://git.lede-project.org/?p=source.git;a=blob;f=target/linux/generic/patches-4.4/254-textsearch_kconfig_hacks.patch;hb=HEAD
I'll certainly have a look at this.
I tried to track the bug down, but it's quite complex. It definitely
looks like it comes from the scripts/kconfig tool upstream, not from
OpenWRT/LEDE.
OpenWRT/LEDE passes all the kernel symbols it wants to select to
scripts/kconfig from Linux, presumably to handle symbol dependencies in
the kernel. But kconfig seems to ignore symbols for which there is no
string description (in the KConfig file that defines the symbol).
That's bad.
Anyway, the problem seems quite easy to reproduce. Just in any
KernelPackage that builds a standalone module, add either a CONFIG_XXX
symbol to KCONFIG:= or a "\nconfig KERNEL_XXX\ndefault y\n\n" to
KernelPackage/$(PKG_NAME)/config. then rebuild.
_______________________________________________
openwrt-devel mailing list
[email protected]
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
