Pango multilib issue

RP,

I have found one common issues for multilib when system config file differ between multilibs.

https://bugzilla.yoctoproject.org/show_bug.cgi?id=2356
This bug caused by modules mechanism in pango:

pango utils, pango-querymodules produce a system config file to indicate where to find the modules when 1st boot, like /usr/{lib64|lib}/pango/1.6.0/modules/ for {x86-64|lib32}-pango respectively.

When installing lib32-pango on sato-image-qemux86-64, lib32 version of pango-querymodules override x86-64 version and produce a system config file with path for lib32 version of modules. Then x86-64 matchbox-desktop failed to open these modules and loaded corrupted fonts.

To resolve this conflict, one possible solution is put the config file and binary under different dir: $LIBDIR for config file, and /usr/{libexec|lib64exec} for config binary(or create different dir under /usr/bin/ for different multilib)

Any comments for this?

Thanks,

Signature · 7 lines

best rgds,
edwin

_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core

Any comments?
I'd like a agreement before any patch:)

Thanks,
Edwin

Quoted 23 lines · Edwin

RP,

I have found one common issues for multilib when system config file differ between multilibs.

https://bugzilla.yoctoproject.org/show_bug.cgi?id=2356
This bug caused by modules mechanism in pango:

pango utils, pango-querymodules produce a system config file to indicate where to find the modules when 1st boot, like /usr/{lib64|lib}/pango/1.6.0/modules/ for {x86-64|lib32}-pango respectively.

When installing lib32-pango on sato-image-qemux86-64, lib32 version of pango-querymodules override x86-64 version and produce a system config file with path for lib32 version of modules. Then x86-64 matchbox-desktop failed to open these modules and loaded corrupted fonts.

To resolve this conflict, one possible solution is put the config file and binary under different dir: $LIBDIR for config file, and /usr/{libexec|lib64exec} for config binary(or create different dir under /usr/bin/ for different multilib)

Any comments for this?

Quoted 30 lines · Edwin

Any comments?
I'd like a agreement before any patch:)

Thanks,
Edwin

Quoted 22 lines · Edwin

RP,

I have found one common issues for multilib when system config file differ between multilibs.

https://bugzilla.yoctoproject.org/show_bug.cgi?id=2356
This bug caused by modules mechanism in pango:

pango utils, pango-querymodules produce a system config file to indicate where to find the modules when 1st boot, like /usr/{lib64|lib}/pango/1.6.0/modules/ for {x86-64|lib32}-pango respectively.

When installing lib32-pango on sato-image-qemux86-64, lib32 version of pango-querymodules override x86-64 version and produce a system config file with path for lib32 version of modules. Then x86-64 matchbox-desktop failed to open these modules and loaded corrupted fonts.

To resolve this conflict, one possible solution is put the config file and binary under different dir: $LIBDIR for config file, and /usr/{libexec|lib64exec} for config binary(or create different dir under /usr/bin/ for different multilib)

Quoted 1 line

Quoted 1 line

Any comments for this?

/libexec and /lib aren't really the correct locations for a configuration file like this.

I think in the mutlilib cases I'd like to move the config file a directory deeper so /etc/pango/${baselib}/pango.modules in the mutliib cases. The standard system file would remain in its existing location.

Cheers,

Richard