From: Joshua Lock <josh@openedhand.com>
To: poky@yoctoproject.org
Subject: Re: a new problem with sstate
Date: Wed, 17 Nov 2010 14:28:43 +0000 [thread overview]
Message-ID: <1290004124.2518.4.camel@scimitar> (raw)
In-Reply-To: <625BA99ED14B2D499DC4E29D8138F1504D31419AED@shsmsx502.ccr.corp.intel.com>
On Wed, 2010-11-17 at 21:21 +0800, Tian, Kevin wrote:
> When looking into the problem why some prebuilts can't be reused, I've struggled with
> another issue these days. It's more severe because the 2nd build can't even succeed
> when prebuilt is used.
>
> The failure happened randomly on eglibc, eglibc-initial, and gcc-runtime. The error log
> shows that either gcc libraries or eglibc headers are not correctly installed when building
> those recipes. This first led me to think about potential dependency problem among
> those recipes. However this only happens when prebuilt is used. A fresh build just
> succeeds.
>
> Finally it turns out from two factors:
>
> o sstate.bbclass has special handling about -initial and -intermediate recipes. If
> a complete (e.g. gcc-cross or eglibc) setscene function has been invoked already,
> installation for those special sstate packages is skipped, while still marked as
> accelerate-able
The special casing in the sstate class was added to work around the fact
that the toolchain bootstrap overwrites some pieces of the sysroot
(bug#239).
http://bugzilla.yoctoproject.org/show_bug.cgi?id=239
If this is still not working is there anything stopping us from
expanding the workaround Richard started in
ecf2eb1efa145d5c8f350697ec605ea58beb9ba7 as a temporary fix until bug
239 is fixed?
http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=ecf2eb1efa145d5c8f350697ec605ea58beb9ba7
Cheers,
Joshua
--
Joshua Lock
Intel Open Source Technology Centre
next prev parent reply other threads:[~2010-11-17 14:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-17 13:21 a new problem with sstate Tian, Kevin
2010-11-17 14:28 ` Joshua Lock [this message]
2010-11-17 14:31 ` Tom Rini
2010-11-18 5:15 ` Tian, Kevin
2010-11-18 6:40 ` Tian, Kevin
2010-11-28 12:20 ` Richard Purdie
2010-11-28 22:12 ` Tom Rini
2010-11-28 23:06 ` Richard Purdie
2010-11-28 23:21 ` Tom Rini
2010-11-29 13:03 ` Richard Purdie
2010-11-18 5:14 ` Tian, Kevin
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=1290004124.2518.4.camel@scimitar \
--to=josh@openedhand.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox