Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: sstate skips STAGING_DIR_KERNEL?
Date: Thu, 23 Jun 2011 16:29:14 +0100	[thread overview]
Message-ID: <1308842954.20015.126.camel@rex> (raw)
In-Reply-To: <4E0286CD.50700@mentor.com>

On Wed, 2011-06-22 at 17:20 -0700, Tom Rini wrote:
> As part of looking into the problem I had that I just posted a patch for
> I was going "why isn't -c clean (or cleanall or cleansstate) knocking
> out STAGING_DIR_KERNEL contents?  Answer, sstate is totally skipping
> that out.  Is there some variable we need to be setting somewhere to add
> this in?  Or are we going to have to take in the various bits of OE.dev
> kernel.bbclass instead here?

I think there is a bug in kernel.bbclass. This should fix it:

diff --git a/meta/classes/kernel.bbclass b/meta/classes/kernel.bbclass
index aaf341b..9f09107 100644
--- a/meta/classes/kernel.bbclass
+++ b/meta/classes/kernel.bbclass
@@ -119,7 +119,7 @@ kernel_do_install() {
        # Support for external module building - create a minimal copy of the
        # kernel source tree.
        #
-       kerneldir=${STAGING_KERNEL_DIR}
+       kerneldir=${D}/kernel
        install -d $kerneldir
 
        #

I'll merge something like this is nobody objects.

Cheers,

Richard





  reply	other threads:[~2011-06-23 15:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-23  0:20 sstate skips STAGING_DIR_KERNEL? Tom Rini
2011-06-23 15:29 ` Richard Purdie [this message]
2011-06-23 16:15   ` Tom Rini
2011-06-23 16:51     ` Tom Rini
2011-06-23 17:12       ` Koen Kooi
2011-06-23 19:47       ` Richard Purdie

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=1308842954.20015.126.camel@rex \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox