From: Gary Thomas <gary@mlbassoc.com>
To: Poky Project <poky@yoctoproject.org>
Subject: sstate info
Date: Thu, 12 Jan 2012 02:57:21 -0700 [thread overview]
Message-ID: <4F0EAE81.8030800@mlbassoc.com> (raw)
I'm trying to understand why sstate sometimes [most times in my case]
is not reusable. Comparing some of the .siginfo files gives me some
info, e.g.
$ bitbake-diffsigs p60_poky/sstate-cache/sstate-pseudo-native-i686-linux-1.2-r4-i686-2-66ad8e10f260d506d065831a738c04a3_populate-sysroot.tgz.siginfo
p60_test_pass1/sstate-cache/sstate-pseudo-native-i686-linux-1.2-r4-i686-2-c7e01d52b467bbe3af0556a43806521a_populate-sysroot.tgz.siginfo
Hash for dependent task virtual:nativepseudo_1.2.bb.do_install changed from 9edd41e331b29f08941225709c325a0d to 9865df7c4aa84fdb288c06faecf63426
How do I figure out what went into the hash(es) that changed?
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next reply other threads:[~2012-01-12 9:57 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-12 9:57 Gary Thomas [this message]
2012-01-12 13:13 ` sstate info Martin Jansa
2012-01-12 13:31 ` Gary Thomas
2012-01-12 13:37 ` Martin Jansa
2012-01-12 15:33 ` Gary Thomas
2012-01-12 16:53 ` McClintock Matthew-B29882
2012-01-12 17:06 ` Gary Thomas
2012-01-12 17:23 ` McClintock Matthew-B29882
2012-01-12 21:07 ` Gary Thomas
2012-01-12 21:12 ` Chris Larson
2012-01-12 21:14 ` McClintock Matthew-B29882
2012-01-13 15:23 ` Gary Thomas
2012-01-13 15:40 ` McClintock Matthew-B29882
2012-01-13 16:27 ` Richard Purdie
2012-01-13 16:53 ` Gary Thomas
2012-01-13 17:11 ` Gary Thomas
2012-01-14 13:30 ` Gary Thomas
2012-01-15 0:06 ` Richard Purdie
2012-01-13 18:09 ` Richard Purdie
2012-01-13 18:19 ` Gary Thomas
2012-01-13 19:36 ` McClintock Matthew-B29882
2012-01-13 18:10 ` Richard Purdie
2012-01-12 21:13 ` McClintock Matthew-B29882
2012-01-12 21:28 ` Gary Thomas
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=4F0EAE81.8030800@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=poky@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.