From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Yevhen Kyriukha <kirgene@gmail.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: Kernel recompile if "rm_work" defined
Date: Wed, 20 Nov 2013 16:53:48 +0000 [thread overview]
Message-ID: <1384966428.16887.74.camel@ted> (raw)
In-Reply-To: <CADV-EXFfYuisF20mV5tuSLFeqxVTBVsOJPsP6n_gJ4uufUEQUA@mail.gmail.com>
On Wed, 2013-11-20 at 13:54 +0200, Yevhen Kyriukha wrote:
> 2013/11/18 Richard Purdie <richard.purdie@linuxfoundation.org>:
> > On Mon, 2013-11-18 at 21:43 +0200, Yevhen Kyriukha wrote:
> >> Hi,
> >>
> >> When I set
> >> INHERIT += "rm_work"
> >> in my local.conf to save some space my kernel now recompiles each time
> >> I run bitbake.
> >>
> >> How to fix this without removing "rm_work" from config?
> >
> > Like this. I keep suggesting someone send me the patch but it never
> > seems to happen...
> >
> > diff --git a/meta/classes/kernel.bbclass b/meta/classes/kernel.bbclass
> > index 383043e..ff99c76 100644
> > --- a/meta/classes/kernel.bbclass
> > +++ b/meta/classes/kernel.bbclass
> > @@ -146,7 +146,6 @@ do_bundle_initramfs () {
> > fi
> > fi
> > }
> > -do_bundle_initramfs[nostamp] = "1"
> >
> > python do_devshell_prepend () {
> > os.environ["LDFLAGS"] = ''
> >
>
> Thanks for the answer but it didn't help.
> Kernel still rebuilds.
Right, the above is the first step in solving this but there is another
issue, the do_bundle_initramfs task is not covered by sstate. We need to
fix the second issue too.
Cheers,
Richard
prev parent reply other threads:[~2013-11-20 16:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-18 19:43 Kernel recompile if "rm_work" defined Yevhen Kyriukha
2013-11-18 21:34 ` Richard Purdie
2013-11-20 11:54 ` Yevhen Kyriukha
2013-11-20 16:53 ` 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=1384966428.16887.74.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=kirgene@gmail.com \
--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 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.