On 10/22/14, 6:07 PM, Burton, Ross wrote:
On 22 October 2014 08:09, Chong Lu <chong...@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

I'm clearly not understanding how our multilib implementation works,
but you don't need many copies of the main gconf package, just one in
the preferred configuration. What is causing multiple copies of gconf
to be installed?

Installing both the lib32 and "regular" version of gconf attempts to install the file "/usr/share/dbus-1/services/org.gnome.GConf.service" twice. (This is normally acceptable, as long as the -contents- of the file are identical.) For whatever reason the contents are different, and the usual way to fix this is to provide a unique file that both versions can include.

This way only one version will be installed, but yet the other service elements will be properly duplicated.

I'd like a bit more information in the commit message indicating what the conflict actually was between both files (since I believe the service file is textual so a diff is easy to include).

--Mark

Ross


--
_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Reply via email to