Re: a new problem with sstate

[Tom Rini <tom_rini@mentor.com>]

On 11/17/2010 07:28 AM, Joshua Lock wrote:
> 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

With old style packaged-staging we workaround this by doing:

# We want to be certain that the scene is set for us only after it's set for
# our dependencies, to avoid problems with pstage package install order.
do_setscene[deptask] = "do_setscene"

Can something similar be done for the sstate way of the world?

-- 
Tom Rini
Mentor Graphics Corporation