Re: Can't select my own Kernel source

[Gary Thomas <gary@mlbassoc.com>]

On 2014-08-08 07:45, filip.ghimpeteanu@freescale.com wrote:
> [Solved] Thank you all for the support.
>
> 1. The solution for the kernel selection was to have the "recipes-kernel/linux" directory structure inside my layer and
> to add my recipe and defconfig in the "recipes-kernel/linux" directory. I added the PREFERRED_PROVIDER_virtual/kernel="linux-yocto-myproj" and the
> PREFERRED_VERSION_linux-yocto-myproj = "3.10%" inside "my conf/local.conf" file (linux-yocto-myproj was the name of my kernel recipe).
>
> 2. I fixed the Error:
> --------------------------------------------------------------------
> ERROR: Unable to install packages. Command '/home/filip/YOCTO_DISK/fsl-arm-bsp/vybrid2/tmp/sysroots/x86_64-linux/usr/bin/smart --data-dir=/home/filip/YOCTO_DISK/fsl-arm-bsp/vybrid2/tmp/work/twr_vf65gs10-poky-linux-gnueabi/core-image-minimal/1.0-r0/rootfs/var/lib/smart install -y run-postinsts@all packagegroup-core-boot@twr_vf65gs10' returned 1:
> Loading cache...
> Updating cache...               ######################################## [100%]
>
> Computing transaction...error: Can't install kernel-module-hello-0.1-r0@twr_vf65gs10: no package provides kernel-3.15.0-rc2-yocto-standard
>
> ERROR: Function failed: do_rootfs
> ERROR: Logfile of failure stored in: /home/filip/YOCTO_DISK/fsl-arm-bsp/vybrid2/tmp/work/twr_vf65gs10-poky-linux-gnueabi/core-image-minimal/1.0-r0/temp/log.do_rootfs.26200
> ERROR: Task 7 (/home/filip/YOCTO_DISK/fsl-arm-bsp/sources/poky/meta/recipes-core/images/core-image-minimal.bb, do_rootfs) failed with exit code '1'
> -------------------------------------------------------------
>
> by changing the PR from "r0" to "r1" (in the hello-mod_0.1.bb) to force the recipe to be baked again.
> I think the problem was with having some cached files for the module recipe, although I deleted the build/tmp directory.

A much simpler (and less invasive) way to handle this would be:
   $ bitbake hello-mod -c cleansstate
   $ bitbake hello-mod

Note: you should be using PRSERVER as the whole PR mechanism is
deprecated (and indeed now missing from most recipes)

> Hi Filip
>
>> #   "linux-yocto-myproj"
>> PREFERRED_PROVIDER_virtual/kernel="linux-yocto-myproj"
>> --------------------------------------------------------------
>>
>> So from my output it turns out that it uses my version. Right?
>
> Yes.
> Actually it only verifies that the variable is correctly set and that the reason it does not use your version is somewhere else.
>
>
> What you could also try is to build your kernel recipe directly to see if bitbake actually does parse your recipe and to see if bitbake thinks your recipe is compatible with the machine your building it for.
> e.g.
> MACHINE=twr-vf65gs10 bitbake linux-yocto-myproj
>
> If bitbake does not find it
> - check bblayers.conf (where your local.conf is)
> - check conf/layer.conf in your layer
>
>
> Regards
> Max
>
> --
> _______________________________________________
> meta-freescale mailing list
> meta-freescale@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-freescale
>

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------