From: Martin Jansa <martin.jansa@gmail.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: gconf-native backends broken when reused from sstate?
Date: Wed, 24 Oct 2012 14:16:29 +0200 [thread overview]
Message-ID: <20121024121629.GE3269@jama.jama.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 1402 bytes --]
When building foxtrotgps I get this error:
| GCONF_CONFIG_SOURCE=xml:merged:/OE/jansa-test/shr-core/tmp-eglibc/sysroots/x86_64-linux/etc/gconf/gconf.xml.defaults \
| /OE/shr-core/tmp-eglibc/sysroots/x86_64-linux/usr/bin/gconftool-2 --makefile-install-rule apps_foxtrotgps.schemas
| /bin/mkdir -p '/OE/shr-core/tmp-eglibc/work/armv4t-oe-linux-gnueabi/foxtrotgps-1.1.1-r1/image/usr/share/foxtrotgps'
|
| (gconftool-2:13082): GConf-CRITICAL **: No such file `/OE/jansa-test/shr-core/tmp-eglibc/work/x86_64-linux/gconf-native-3.2.3-r12/GConf-3.2.3/gconf/../backends/.libs/libgconfbackend-xml.so'
|
|
| (gconftool-2:13082): GConf-WARNING **: Failed to load source "xml:merged:/OE/jansa-test/shr-core/tmp-eglibc/sysroots/x86_64-linux/etc/gconf/gconf.xml.defaults": Failed: Couldn't locate backend module for `xml:merged:/OE/jansa-test/shr-core/tmp-eglibc/sysroots/x86_64-linux/etc/gconf/gconf.xml.defaults'
First path points to wrong sysroot (/OE/jansa-test/shr-core is used only
on builder from where i get sstate-cache with SSTATE_MIRROR) and the
other paths to backends are using even WORKDIR.
It's not really foxtrotgps fault:
sysroots/x86_64-linux/usr/bin/gconftool-2 --get-default-source
xml:merged:/OE/jansa-test/shr-core/tmp-eglibc/sysroots/x86_64-linux/etc/gconf/gconf.xml.defaults
Anyone seen this?
Cheers,
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
next reply other threads:[~2012-10-24 12:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-24 12:16 Martin Jansa [this message]
2012-10-24 12:26 ` gconf-native backends broken when reused from sstate? Richard Purdie
2012-10-24 14:35 ` Burton, Ross
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=20121024121629.GE3269@jama.jama.net \
--to=martin.jansa@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.