From: Tomas Frydrych <tf+lists.yocto@r-finger.com>
To: yocto@yoctoproject.org
Subject: Re: RaspberryPi Kernel - sometimes it works, sometimes it doesn't
Date: Mon, 11 Jun 2012 08:29:33 +0100 [thread overview]
Message-ID: <4FD59E5D.4080008@r-finger.com> (raw)
In-Reply-To: <1B44395A-0DD8-4136-83B3-FD82C9F5DDCA@keylevel.com>
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.
Tomas
next prev parent reply other threads:[~2012-06-11 7:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-10 11:30 RaspberryPi Kernel - sometimes it works, sometimes it doesn't Chris Tapp
2012-06-11 7:29 ` Tomas Frydrych [this message]
2012-06-11 7:58 ` Chris Tapp
2012-06-11 13:53 ` Khem Raj
2012-06-11 16:29 ` Paul Eggleton
2012-06-12 7:23 ` Tomas Frydrych
2012-06-12 11:26 ` Paul Eggleton
2012-06-12 11:30 ` Gary Thomas
2012-06-13 13:17 ` Paul Eggleton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4FD59E5D.4080008@r-finger.com \
--to=tf+lists.yocto@r-finger.com \
--cc=yocto@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.