I am currently working on an bbappend for linux-omapl138-psp_2.6.37.bb for the 
am180x-evm machine and I am having a problem with my custom defconfig not being 
used. When bitbaking the recipe my defconfig is copied to the ${WORKDIR} like 
it is supposed to but after the kernel is built I noticed the .config within 
${S} was significantly different than ${WORKDIR}/defconfig. This problem was 
detected when the uImage I ran did not have support for oprofile even though my 
defconfig does include the support. I did some searching I found the 
${S}/.config is the same as 
meta-ti/recipes-kernel/linux/linux-omap138-psp-2.6.37/am180x-evm/configs/static.

After some debugging I found the problems lies within compileconfigs task which 
is defined in multi-kernel.inc.

Compileconfigs renames ${WORKDIR}/defconfig to ${WORKDIR}/defconfig.save. Then 
it loops through all the defconfigs in the ${WORKDIR}/configs directory and 
configures, compiles, install and deploys the kernel for each of the 
defconfigs. The final step is to restore the original defconfig file by 
renaming ${WORKDIR}/defconfig.save to ${WORKDIR}/defconfig. After 
compileconfigs is done do_configure is ran using ${WORKDIR}/defconfig and the 
usual build steps are completed.

However, the problem is the patch "Multi-kernel: fix get_kernelversion returns 
None for do_compileconfigs" causes compileconfigs to run after do_configure 
instead of before it. Therefore, ${WORKDIR}/defconfig is never copied to 
${S}/.config and the kernel is never configured to use this .config. The last 
.config used by do_compileconfigs to compile the kernel is used instead.

I thought a simple solution would be to call do_configure at the end of 
compileconfigs but then I get a series of
"basename: missing operand"
and
make: *** No rule to make target `oldconfig`. Stop"

Any suggestions on how to fix this problem? This should issue be affecting 
anyone who is using a kernel that includes multi-kernel.inc.

Regards,
Franklin Cooper Jr.
Texas Instruments
Application Engineer
[email protected]<mailto:[email protected]>

_______________________________________________
meta-ti mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/meta-ti

Reply via email to