From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: openembedded-core@lists.openembedded.org,
openembedded-commits@lists.openembedded.org
Subject: Re: [oe-commits] Laurentiu Palcu : add fontcache.bbclass
Date: Thu, 07 Feb 2013 22:40:02 +0000 [thread overview]
Message-ID: <1360276802.10722.55.camel@ted> (raw)
In-Reply-To: <20130206233409.GJ3271@jama>
On Thu, 2013-02-07 at 00:34 +0100, Martin Jansa wrote:
> On Wed, Feb 06, 2013 at 10:17:10PM +0100, Martin Jansa wrote:
> > On Wed, Feb 06, 2013 at 02:08:41PM +0200, Laurentiu Palcu wrote:
> > It fails only on some machines I'm building (3 machines from 6) and only sometimes (last run it was only on 2 from 6)
> >
> > Now I was running it manually and got nice error finally:
> > Running intercept scripts:
> > > Executing update_font_cache
> > readelf: Error:
> > '/OE/shr-core/tmp-eglibc/work/tuna-oe-linux-gnueabi/shr-image/2.0-r20/rootfs/usr/bin/fc-cache':
> > No such file
> > ERROR: intercept script "update_font_cache" failed!
> >
> > So something is pulling interceptor without runtime dependency on
> > fontconfig.
>
> In the end it wasn't fs-cache missing, but
> /usr/bin/crossscripts/qemuwrapper in some sysroots
>
> bitbake -c cleansstate qemuwrapper-cross
> for each MACHINE and building it again resolved that..
The sstate package for this recipe was corrupted. There is a fix in
master for this and a few other issues this patchset raised.
Cheers,
Richard
prev parent reply other threads:[~2013-02-07 22:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20130206093802.16EA32097@opal>
2013-02-06 11:56 ` [oe-commits] Laurentiu Palcu : add fontcache.bbclass Martin Jansa
2013-02-06 12:08 ` Laurentiu Palcu
2013-02-06 21:17 ` Martin Jansa
2013-02-06 23:34 ` Martin Jansa
2013-02-07 22:40 ` Richard Purdie [this message]
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=1360276802.10722.55.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=martin.jansa@gmail.com \
--cc=openembedded-commits@lists.openembedded.org \
--cc=openembedded-core@lists.openembedded.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