trying to enable CONFIG_AUTOFS4_FS in the kernel for my custom machine my_mach using Yocto Project
I'm trying to enable
CONFIG_AUTOFS4_FS
in the kernel for my custom machine my_mach
using Yocto Project, but it's not reflected in the final image.
Observe my set up:
-Base layer: meta-xxx-yyy
-Custom layer: meta-xxx-mylayer
I took this steps to try trouble shoot
-Added CONFIG_AUTOFS4_FS=y
to a fragment file (frag.cfg
) in
-Included the fragment file in linux_git.bbappend
using SRC_URI += "file://frag.cfg"
-Set COMPATIBLE_MACHINE_my_mach = "my_mach"
in linux_git.bbappend
-Built the kernel using bitbake linux -c cleansstate -f; bitbake linux -c configure -f; etc.
The build completes successfully.
CONFIG_AUTOFS4_FS
is not set in the final image .
My custom layer meta-xxx-mylayer
seems functional .
frag.cfg
is copied to a different directory than the main kernel source git
.
What could be causing CONFIG_AUTOFS4_FS
to not be enabled despite the fragment file?
Is the location difference between frag.cfg
and the main source a potential issue?
@Middleware & OS6 Replies
I have seen this issues before . The location can pose as the an issue, if there is a specific
.cfg
file that needs to include the new fragment. Sometimes, you need to add the fragment to a KERNEL_FEATURES
or similar variable. An example is that you might need to use:
KERNEL_FEATURES_append = " features/frag.cfg"
Try doing this @Marvee Amasi@Marvee Amasi
You have to ensure that the frag.cfg file is being copied to the correct location. Because the fragment file should be copied to the right directory within the kernel source tree for it to be considered during the configuration step.
You have to verify that the linux_git.bbappend file is correctly added to the layer metadata. Check that the file's location is correct, and make sure that the COMPATIBLE_MACHINE_my_mach variable is set in the linux_git.bbappend file.
Ah I think I haven't verified the metadata inclusion yet. Just to confirm, should I be looking for
linux_git.bbappend
in a specific file within the metadata, like a Makefile or something similar? @Boss ladySomething similar depending on the nature of your code
Oh okay