[yocto] kernel config fragments not applied

Schmitt, Richard Richard.Schmitt at commscope.com
Tue Jan 10 10:05:15 PST 2017


I am having a heck of a hard time getting a minor kernel config fragment applied.

In order to minimize all variables, I am simply trying to build linux-yocto for a qemux86 MACHINE target.

There had been some discussion on the mailing list previously that suggested making sure linux-yocto.inc was included within the recipes.   The ones being used are standard poky recipes and they do include the linux-yocto.inc file.

My configuration is very simple.  I have my own layer and linux-yocto bbappend:

meta-mylayer/recipes-kernel/linux/linux-yocto_4.4.bbappend

Whose contents are:

FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"

SRC_URI += " \
        file://overlayfs.cfg \
        "

With the config fragment in:

meta-mylayer/recipes-kernel/linux/linux-yocto/overlayfs.cfg

whose contents is:

CONFIG_OVERLAY_FS=y

If I do a "bitbake linux-yocto" I would expect it to generate a config file that includes CONFIG_OVERLAY_FS=y and a kernel that includes this filesystem.  I don't.

My layer is parsed correctly and the bbappend is found and parsed.  I know this because in the tmp directory:

tmp/work/qemux86-poky-linux/linux-yocto/4.4.26+gitAUTOINC+3030330b06_ca6a08bd7f-r0/

the file overlayfs.cfg exists.

Searching the log files, the only one that references this file though is log.do_unpack.  I do not see any reference to it in log.do_kernel_configme or log.do_configure.    I'm not sure how kernel fragments are applied, but looking through the classes and recipes for linux-yocto in poky/meta, I do not see any code that would apply kernel fragments.  So I'm not sure if I'm missing some piece.

Searching through the files in poky/meta, I find meta-config.sh only in recipes-core/uclibc and recipes-core/busybox.  That's why I think I'm missing something.

I'm using the krogoth branch of poky.

What am I missing?

Thanks,
Rich


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/yocto/attachments/20170110/2228b981/attachment.html>


More information about the yocto mailing list