From: Gary Thomas <gary@mlbassoc.com>
To: "Zhai, Edwin" <edwin.zhai@intel.com>
Cc: Poky <poky@lists.pokylinux.org>
Subject: Re: Is sstate broken
Date: Thu, 03 Mar 2011 05:56:56 -0700 [thread overview]
Message-ID: <4D6F9018.1000605@mlbassoc.com> (raw)
In-Reply-To: <4D6B3BA3.9050303@intel.com>
On 02/27/2011 11:07 PM, Zhai, Edwin wrote:
> Gary,
>
> Thanks for trying this.
> sstate function is a little bit fragile recently. I'll look at it after fixing some other bugs.
Any progress on this?
Should I file this as a bug?
> Gary Thomas wrote:
>>
>> I tried to run an experiment with SSTATE_MIRRORS on the latest master.
>> From what I can tell, this is 100% not working, although I may just
>> not have set it up properly. Here's what I did:
>>
>> * Build Poky for my platform in /local/xyz_ppc_poky
>> * Set up to build exact same machine/config/etc in /local/xyz_test
>> pointing SSTATE_MIRRORS at /local/xyz_ppc_poky/sstate-cache by
>> adding these lines to local.conf (only configuration change)
>> SSTATE_MIRRORS ?= "\
>> file://.* file:///local/xyz_ppc_poky/sstate-cache/"
>>
>> The end result is that both builds built (from scratch) the same
>> set of packages. There seems to be no reuse of anything from
>> the SSTATE_MIRRORS.
>>
>> $ du /local/xyz_ppc_poky/* -s
>> 20 /local/xyz_ppc_poky/conf
>> 1456 /local/xyz_ppc_poky/downloads
>> 4 /local/xyz_ppc_poky/pseudodone
>> 1010392 /local/xyz_ppc_poky/sstate-cache
>> 14434076 /local/xyz_ppc_poky/tmp
>>
>> $ du -s /local/xyz_test
>> 20 /local/xyz_test/conf
>> 1456 /local/xyz_test/downloads
>> 4 /local/xyz_test/pseudodone
>> 1010276 /local/xyz_test/sstate-cache
>> 14425860 /local/xyz_test/ tmp
>>
>> The full build log of the second run is at http://www.mlbassoc.com/poky/build_ppc_with_sstate
>> Notice the many lines which say that a particular step failed. I can't see the reason, nor
>> can I find any corresponding log file to help me out. An example is:
>> ERROR: Task 0 (virtual:native:/home/local/poky-amltd/meta/recipes-devtools/pseudo/pseudo_1.0.bb, do_unpack) failed with exit code '1'
>>
>> Am I missing something? Now that the build with BB_NO_NETWORK is working well,
>> this is my last hurdle to making Poky truly useful for my customers.
>>
>> Thanks
>>
>> --
>> ------------------------------------------------------------
>> Gary Thomas | Consulting for the
>> MLB Associates | Embedded world
>> ------------------------------------------------------------
>> _______________________________________________
>> poky mailing list
>> poky@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/poky
>>
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next prev parent reply other threads:[~2011-03-03 12:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-24 15:14 Is sstate broken Gary Thomas
2011-02-28 6:07 ` Zhai, Edwin
2011-03-03 12:56 ` Gary Thomas [this message]
2011-03-04 1:59 ` Zhai, Edwin
2011-03-04 11:34 ` Gary Thomas
2011-03-09 1:29 ` Richard Purdie
2011-03-09 18:42 ` Gary Thomas
2011-03-09 19:04 ` Richard Purdie
2011-03-09 19:30 ` Koen Kooi
2011-03-09 21:51 ` Khem Raj
2011-03-09 23:04 ` Richard Purdie
2011-03-09 20:26 ` 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=4D6F9018.1000605@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=edwin.zhai@intel.com \
--cc=poky@lists.pokylinux.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