From: Marcin Juszkiewicz <marcin.juszkiewicz@linaro.org>
To: openembedded-core@lists.openembedded.org
Subject: Can we trust to sstate-cache?
Date: Thu, 18 Oct 2012 15:36:25 +0200 [thread overview]
Message-ID: <508005D9.2060507@linaro.org> (raw)
Today I bumped gcc-linaro from 4.7-r5 to 4.7-r6. First version was plain
2012.10 release while second one was tarball from bzr repository with
huge set of ICE related fixes for AArch64 architecture.
To do fast clean build I removed TMPDIR and started new build of
core-image-minimal target.
But then I noticed ugly thing:
0: eglibc-2.16-r18+svnr20393 do_populate_sysroot_setscene (pid 30106)
1: eglibc-2.16-r18+svnr20393 do_package_setscene (pid 30107)
3: eglibc-initial-2.16-r18+svnr20393 do_package_setscene (pid 28921)
Why eglibc was taken from sstate-cache instead of being rebuilt (like it
was with 'db')? This makes me sad as it shows that I cannot trust
sstate-cache so each new build will take hours instead of minutes.
Or maybe I am wrong?
next reply other threads:[~2012-10-18 13:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-18 13:36 Marcin Juszkiewicz [this message]
2012-10-18 17:08 ` Can we trust to sstate-cache? McClintock Matthew-B29882
2012-10-18 17:43 ` 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=508005D9.2060507@linaro.org \
--to=marcin.juszkiewicz@linaro.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 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.