Re: RaspberryPi Kernel - sometimes it works, sometimes it doesn't

[Khem Raj <raj.khem@gmail.com>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 6/11/2012 12:29 AM, Tomas Frydrych wrote:
> Hi,
> 
> On 10/06/12 12:30, Chris Tapp wrote:
>> I've been building the 3.1.9 Raspberry Pi kernel under Denzil
>> using the meta layer at
>> https://github.com/djwillis/meta-raspberrypi. This uses a kernel
>> recipe based on the git repository at 
>> https://github.com/raspberrypi/linux/commits/rpi-patches.
>> 
>> Some of the kernel commit IDs (e.g. 
>> 94fbbc4e3988075abad0d3b32842b82c590324fc) seem to build ok, but
>> they don't always run. As in, if I -c clean and build then
>> sometimes I end up with a bootable image, sometimes I don't. I'm
>> not changing anything else in the build environment.
>> 
>> Any ideas what can cause this?
> 
> I find that -c clean does not work very well, afterward the package
> gets recompiled but instead of the actual package packages being
> rebuilt, an earlier version of the packages gets pulled out of
> sstate into the image. I definitely saw this behaviour with Yocto
> kernels, but I think happens with other packages as well; I always
> do -c cleansstate now to avoid this.

yes thats the intended behavior if nothing changed that ensues a
recompile then it will use precompiled sstate for the package

> 
> Tomas _______________________________________________ yocto mailing
> list yocto@yoctoproject.org 
> https://lists.yoctoproject.org/listinfo/yocto

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk/V+FwACgkQuwUzVZGdMxRlnwCfaIy1wo/G0gEIVbQQe0ImsKPa
2csAoJGhol1N0xrudHfT/c7T97Hoizhf
=l1iC
-----END PGP SIGNATURE-----