From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: Koen Kooi <koen@dominion.thruhere.net>
Subject: Re: sstate skips STAGING_DIR_KERNEL?
Date: Thu, 23 Jun 2011 20:47:54 +0100 [thread overview]
Message-ID: <1308858474.20015.141.camel@rex> (raw)
In-Reply-To: <4E036F1C.1080609@mentor.com>
On Thu, 2011-06-23 at 09:51 -0700, Tom Rini wrote:
> On 06/23/2011 09:15 AM, Tom Rini wrote:
> > On 06/23/2011 08:29 AM, Richard Purdie wrote:
> >> 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.
> >
> > That makes sense, testing this now.
>
> Yeah, that does it.
>
> Tested-by: Tom Rini <tom_rini@mentor.com>
>
> Koen, once this is in oe-core need a request to bring it over too or
> just want to come grab it?
I've merged it into OE-Core.
Cheers,
Richard
prev parent reply other threads:[~2011-06-23 19:51 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
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 [this message]
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=1308858474.20015.141.camel@rex \
--to=richard.purdie@linuxfoundation.org \
--cc=koen@dominion.thruhere.net \
--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