Openembedded Core Discussions
 help / color / mirror / Atom feed
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 18:02:09 +0800	[thread overview]
Message-ID: <543CF4A1.9070509@windriver.com> (raw)
In-Reply-To: <CAJTo0LZQvykUoraK6b7gRyhi0V3fNsubOQ60SD0q+GphX96gHw@mail.gmail.com>


On 10/14/2014 05:59 PM, Burton, Ross wrote:
> On 14 October 2014 10:58, Chong Lu <Chong.Lu@windriver.com> wrote:
>> Do you mean we should put /usr/lib64/gconf/gconfd-2 into lib64gconf and
>> /usr/lib/gconf/gconfd-2 into lib32gconf?
> No, the binary gconfd-2 goes into a separate package, such as gconf.
>
> Ross
>

Got it. Thanks

//Chong




      reply	other threads:[~2014-10-14 10:02 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
2014-10-14  9:59       ` Burton, Ross
2014-10-14 10:02         ` Chong Lu [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=543CF4A1.9070509@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox