From: Chong Lu <Chong.Lu@windriver.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] gconf: fix multilib conflict - org.gnome.GConf.service
Date: Tue, 14 Oct 2014 17:58:03 +0800 [thread overview]
Message-ID: <543CF3AB.9030301@windriver.com> (raw)
In-Reply-To: <CAJTo0La_gxKvJ3TqiimF4C6tMNmCay7_=NSQSTqo8itTANCtPw@mail.gmail.com>
On 10/14/2014 05:52 PM, Burton, Ross wrote:
> On 14 October 2014 09:39, Chong Lu <Chong.Lu@windriver.com> wrote:
>> The gconfd-2 will be called in org.gnome.GConf.service file and the path of
>> gconfd-2 is ${libexecdir}, this will get following error when multilib exported
>> in the sdk:
>> error: file /usr/share/dbus-1/services/org.gnome.GConf.service from install
>> of gconf-3.2.6-r0.0.lib32_x86 conflicts with file from package
>> gconf-3.2.6-r0.0.x86_64
>>
>> Changed ${libexecdir} to /usr/libexec to fix this issue.
> Haven't we been here before? A better fix is to split the library and
> the daemon into separate packages, so in a multilib environment you
> have lib32gconf, lib64gconf, and gconfd (which can be 32- or 64-bit).
>
> Ross
>
>
Hi Ross,
Do you mean we should put /usr/lib64/gconf/gconfd-2 into lib64gconf and
/usr/lib/gconf/gconfd-2 into lib32gconf?
Best Regards
Chong
next prev parent reply other threads:[~2014-10-14 9:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-14 8:39 [PATCH 0/1] gconf: fix multilib conflict - org.gnome.GConf.service Chong Lu
2014-10-14 8:39 ` [PATCH 1/1] " Chong Lu
2014-10-14 9:52 ` Burton, Ross
2014-10-14 9:58 ` Chong Lu [this message]
2014-10-14 9:59 ` Burton, Ross
2014-10-14 10:02 ` Chong Lu
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=543CF3AB.9030301@windriver.com \
--to=chong.lu@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.com \
/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.