From: Gary Thomas <gary@mlbassoc.com>
To: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: What keeps sstate from being used?
Date: Wed, 6 Jul 2016 12:10:42 +0200 [thread overview]
Message-ID: <577CD922.4000405@mlbassoc.com> (raw)
I just had a [nearly] complete build failed (building webkitgtk
after some 6000 tasks). I decided to try the 'rebuild from sstate'
by removing my 'tmp' directory and rebuild. Bitbake proceeded to
run 2200 setscene tasks and then [it seems] started over on the
build, rebuilding the target gcc, the kernel, who knows what else...
These are all things that I thought had been completed before
during the initial ~6000 steps.
What could be going on and why couldn't it just pick up using
sstate from where it left off?
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next reply other threads:[~2016-07-06 10:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-06 10:10 Gary Thomas [this message]
2016-07-06 11:51 ` What keeps sstate from being used? Chris Z.
2016-07-06 13:25 ` Daniel.
2016-07-06 14:23 ` Gary Thomas
2016-07-06 14:27 ` Burton, Ross
2016-07-06 14:39 ` Gary Thomas
2016-07-06 21:56 ` Chris Z.
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=577CD922.4000405@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=yocto@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.