On 10/15/2014 06:42 PM, Burton, Ross wrote:
On 15 October 2014 03:54, Chong Lu <[email protected]> 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
Split org.gnome.GConf.service to ${PN}-service, the conflict was fixed.
Why are both ML variants of gconf being installed? Presumably for
libgconf, which needs to have ML variants and is packaged into $PN.
$PN also contains the binaries and data files, which are not
ML-specific and can only be installed once.
So, gconf should split the daemon/binaries from the libraries. I
suggested this back in July as it seems the logical answer, instead of
splitting the daemon binary and the service file that defines where
the binary is.
Ross
Hi Ross,
Sorry, I don't understand your solution.
In org.gnome.GConf.service.in file, it has following line:
Exec=@libexecdir@/gconfd-2
And then, in Makefile.am file:
org.gnome.GConf.service: $(srcdir)/org.gnome.GConf.service.in
sed -e 's,[@]libexecdir[@],$(libexecdir),g' \
<$(srcdir)/org.gnome.GConf.service.in
>org.gnome.GConf.service
In 32bit and 64bit environment, the path of gconfd-2 is different.
So, if we want to install both gconf and lib32-gconf in a image, the
error will get as above.
In fact, I want to resolve this confliction. Do you have any suggestions?
Best Regards
Chong
--
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core
