From: Martin Jansa <martin.jansa@gmail.com>
To: Yi Qingliang <niqingliang2003@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: kernel and boost will recompile every time
Date: Wed, 27 Nov 2013 03:03:36 +0100 [thread overview]
Message-ID: <20131127020336.GO2870@jama> (raw)
In-Reply-To: <72922584.TJuWgrnFYb@yiqingliang-pc>
[-- Attachment #1: Type: text/plain, Size: 560 bytes --]
On Wed, Nov 27, 2013 at 09:51:22AM +0800, Yi Qingliang wrote:
> Hello.
>
> I know the kernel will recompile every time for recent update, and I
> found the boost will also do like that, even I have sstate cache in my own
> server.
>
> How to debug this problem?
kernel rebuilding was fixed few days ago, do you have latest revision?
You can use scripts/sstate-diff-machines.sh to "store" the signatures
and then compare them when you notice something unexpectedly rebuilding.
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
next prev parent reply other threads:[~2013-11-27 2:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-27 1:51 kernel and boost will recompile every time Yi Qingliang
2013-11-27 2:03 ` Martin Jansa [this message]
2013-11-27 2:26 ` Yi Qingliang
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=20131127020336.GO2870@jama \
--to=martin.jansa@gmail.com \
--cc=niqingliang2003@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox