From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] pango: use qemu to generate pango.modules during rootfs construction
Date: Tue, 13 Sep 2011 18:08:16 +0100 [thread overview]
Message-ID: <1315933706.13526.11.camel@ted> (raw)
In-Reply-To: <1315655628.4368.14.camel@lenovo.internal.reciva.com>
On Sat, 2011-09-10 at 12:53 +0100, Phil Blundell wrote:
> On Sat, 2011-09-10 at 10:54 +0100, Richard Purdie wrote:
> > which looks right. It does crash as part of rpm rootfs generation
> > though, possibly something to do with pseudo given the root operation it
> > attempts. Did you test this against rpm or ipk?
>
> Ah, right, I was testing with ipk. Maybe that's the difference.
I think the recent pseudo environment fixes which I ran into in other
areas have helped with this. Rather than a segfault, I now see:
Adding system startup for /media/data1/build1/poky/build/tmp/work/qemux86-poky-linux/core-image-sato-1.0-r0/rootfs/etc/init.d/ofono.
qemu: Unsupported syscall: 240
qemu: Unsupported syscall: 240
(pango-querymodules:10498): GLib-WARNING **: getpwuid_r(): failed due to unknown user id (1000)
qemu: Unsupported syscall: 240
with the unsppported syscall issues being due to the lack of
multithreading support in qemu user mode emulation on x86. I suspect the
problem was that it was running in pseudo context when it shouldn't have
been and since it was root, it tried to do things as root which it
couldn't do.
Despite the above messages, it does now "work" on 32 bit x86 targets
however the warning message about the invalid user is yet another sign
of us needing to better think through this though more carefully (and
further test things) :/.
I've therefore taken the decision to revert this since I really want to
stablise for the release at this point and I'm not filled with
confidence that there aren't other problems lurking here.
Cheers,
Richard
next prev parent reply other threads:[~2011-09-13 17:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-31 15:35 [PATCH] pango: use qemu to generate pango.modules during rootfs construction Phil Blundell
2011-09-08 1:12 ` Saul Wold
2011-09-09 21:19 ` Saul Wold
2011-09-10 8:24 ` Richard Purdie
2011-09-10 9:28 ` Phil Blundell
2011-09-10 9:54 ` Richard Purdie
2011-09-10 11:53 ` Phil Blundell
2011-09-13 17:08 ` Richard Purdie [this message]
2011-09-13 17:14 ` Otavio Salvador
2011-09-13 17:25 ` Phil Blundell
2011-09-13 18:33 ` Otavio Salvador
2011-09-13 18:46 ` Saul Wold
2011-09-14 9:10 ` Phil Blundell
2011-09-11 21:33 ` Phil Blundell
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=1315933706.13526.11.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.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