From: Laurentiu Palcu <laurentiu.palcu@intel.com>
To: Phil Blundell <philb@gnu.org>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] pango: have postinstalls run at do_rootfs time
Date: Thu, 20 Dec 2012 17:47:23 +0200 [thread overview]
Message-ID: <50D3330B.1020202@intel.com> (raw)
In-Reply-To: <1356016878.24487.187.camel@phil-desktop>
On 12/20/2012 05:21 PM, Phil Blundell wrote:
> On Wed, 2012-12-19 at 18:03 +0200, Laurentiu Palcu wrote:
>> Since pango-native is built anyway and all the modules are in the native
>> sysroot, create the cache file by scanning those files instead of the
>> target files. The latter will fail because the shared objects wouldn't
>> be from the same ELF class.
>
> Is it guaranteed that the native build will have the same set of
> modules? It seems to me that it would be safer to scan the target ones
> under qemu as you did for gtk-immodules.
AFAIK pango-native builds all modules. I suppose I could also do it as I
did it for matchbox-keyboard package but I'd always prefer to avoid qemu
overhead whenever we can do it entirely natively.
Thanks,
Laurentiu
>
> p.
>
>
next prev parent reply other threads:[~2012-12-20 16:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-19 16:03 [PATCH] pango: have postinstalls run at do_rootfs time Laurentiu Palcu
2012-12-20 9:55 ` Laurentiu Palcu
2012-12-20 15:21 ` Phil Blundell
2012-12-20 15:47 ` Laurentiu Palcu [this message]
2012-12-20 15:59 ` Burton, Ross
2012-12-20 16:21 ` Laurentiu Palcu
2012-12-20 16:29 ` Burton, Ross
2012-12-20 16:40 ` Otavio Salvador
-- strict thread matches above, loose matches on Subject: below --
2012-12-19 19:13 Laurentiu Palcu
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=50D3330B.1020202@intel.com \
--to=laurentiu.palcu@intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=philb@gnu.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