From: Richard Purdie <rpurdie@linux.intel.com>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: poky@yoctoproject.org
Subject: Re: sstate status
Date: Fri, 03 Dec 2010 14:11:45 -0800 [thread overview]
Message-ID: <1291414305.14277.2746.camel@rex> (raw)
In-Reply-To: <201012031634.56033.paul.eggleton@linux.intel.com>
Hi,
On Fri, 2010-12-03 at 16:34 +0000, Paul Eggleton wrote:
> I've been doing some tests with sstate, and I've managed to get to a
> stage where I can share the SSTATE_DIR between my two machines (one
> running Fedora 14 and the other Kubuntu 10.10) and almost get a
> successful build from a clean TMPDIR. My last test got to
> poky-image-minimal.do_rootfs and then failed due to some kind of
> package dependency issue:
>
> --------- snip ---------
> | Processing rpm...
> | Processing zypper...
> | error: Failed dependencies:
> | elfutils >= 0.148 is needed by rpm-5.1.10-r7.i586
> | libaugeas0 >= 0.7.3 is needed by zypper-1.4.7+git0
> +9eb0e248e06c8d20ad054be2439149d9ede37531-r1.i586
> | ERROR: Task failed: ('function do_rootfs failed',
> '/home/pokystuff/tmp/work/qemux86-poky-linux/poky-image-minimal-1.0-r0/temp/log.do_rootfs.6874')
> --------- snip ---------
>
> A "bitbake -c clean augeas elfutils" and then "bitbake
> poky-image-minimal" again went through OK (and built the
> aforementioned recipes from sstate) , so I'm not sure what went wrong
> here.
>
> My current state of work is in the paule/sstate contrib branch, which
> is based on Kevin's tk/sstate branch. Kevin, I think the sooner we can
> move this towards master the better, then we can get some wider
> testing.
>
> FYI Joshua has made bug #507 into a tracking bug for current sstate issues:
> http://bugzilla.pokylinux.org/show_bug.cgi?id=507
Kevin/Paul:
I notice a number of patches in your branches which shouldn't be needed
if we use the two patches at the head of:
http://git.pokylinux.org/cgit/cgit.cgi/poky-contrib/log/?h=rpurdie/tweaks2
Could you please test using those two changes, or let me know if those
changes cause problems.
Cheers,
Richard
next prev parent reply other threads:[~2010-12-03 22:12 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-03 16:34 sstate status Paul Eggleton
2010-12-03 22:11 ` Richard Purdie [this message]
2010-12-05 11:10 ` Tian, Kevin
2010-12-06 1:29 ` Richard Purdie
2010-12-07 7:46 ` Tian, Kevin
2010-12-07 15:02 ` Richard Purdie
2010-12-08 0:40 ` Tian, Kevin
2010-12-06 16:06 ` Paul Eggleton
2010-12-07 12:46 ` Richard Purdie
2010-12-07 16:36 ` Paul Eggleton
2010-12-08 11:22 ` Tian, Kevin
2010-12-08 11:31 ` Paul Eggleton
2010-12-08 11:41 ` Tian, Kevin
2010-12-03 23:31 ` Gary Thomas
2010-12-04 12:47 ` Gary Thomas
2010-12-05 11:19 ` Tian, Kevin
2010-12-05 12:02 ` Gary Thomas
2010-12-06 11:19 ` Gary Thomas
[not found] ` <4CFCC607.9040803@mlbassoc.com>
2010-12-07 7:17 ` Tian, Kevin
2010-12-05 11:07 ` Tian, Kevin
-- strict thread matches above, loose matches on Subject: below --
2010-12-08 14:02 Paul Eggleton
2010-12-08 14:06 ` Paul Eggleton
2010-12-08 14:15 ` Tian, Kevin
2010-12-08 14:50 ` Paul Eggleton
2010-12-08 14:52 ` Tian, Kevin
2010-12-08 14:41 ` Gary Thomas
2010-12-08 15:31 ` Gary Thomas
2010-12-08 15:55 ` Paul Eggleton
2010-12-08 17:14 ` Paul Eggleton
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=1291414305.14277.2746.camel@rex \
--to=rpurdie@linux.intel.com \
--cc=paul.eggleton@linux.intel.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