Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Zhai, Edwin" <edwin.zhai@intel.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Pango multilib issue
Date: Thu, 26 Apr 2012 15:53:22 +0800	[thread overview]
Message-ID: <20120426075321.GG1450@edwin-gen> (raw)

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,


-- 
best rgds,
edwin



             reply	other threads:[~2012-04-26  7:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-26  7:53 Zhai, Edwin [this message]
2012-04-27  8:20 ` Pango multilib issue Zhai, Edwin
2012-04-27 10:45   ` Richard Purdie
2012-04-28  1:15     ` Zhai, Edwin

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=20120426075321.GG1450@edwin-gen \
    --to=edwin.zhai@intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.org \
    /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