From: Phil Blundell <philb@gnu.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: Sat, 10 Sep 2011 10:28:11 +0100 [thread overview]
Message-ID: <1315646891.4368.13.camel@lenovo.internal.reciva.com> (raw)
In-Reply-To: <1315643085.1986.24.camel@ted>
On Sat, 2011-09-10 at 09:24 +0100, Richard Purdie wrote:
> For what its worth, even on plain qemux86 I'm seeing:
>
> qemu: Unsupported syscall: 240
> inb: port=0x0000
> qemu: uncaught target signal 11 (Segmentation fault) - core dumped
> /media/data1/build1/poky/build/tmp/work/qemux86-poky-linux/core-image-sato-1.0-r0/rootfs/etc/rpm-postinsts/pango-module-basic-fc.sh: line 8: 11084 Segmentation fault PSEUDO_RELOADED=YES qemu-i386 -L $D $D/usr/bin/pango-querymodules > "$D/etc/pango/pango.modules"
>
> in the rootfs logs. Which reading things online suggests that qemu
> doesn't support multithreading under qemu user emulation on i386.
That is rather strange. It does work ok for me on mips, and I wasn't
able to make it go wrong on x86-64 either in a quick test.
The other odd thing is that, from a quick look at the qemu source code,
it does seem as though sys_futex (which is syscall 240 on i386 and
syscall 202 on x86-64) ought to be supported if qemu was built with NPTL
on. However, in my x86-64 test I did see the "unsupported syscall 202"
syscall although the binary still seemed to run fine.
And, well, the third weird thing is that your log message above implies
that pango-querymodules is trying to do inb(0) which clearly is not
going to work if you're not root. I've no idea why it would be wanting
to do that.
p.
next prev parent reply other threads:[~2011-09-10 9:33 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 [this message]
2011-09-10 9:54 ` Richard Purdie
2011-09-10 11:53 ` Phil Blundell
2011-09-13 17:08 ` Richard Purdie
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=1315646891.4368.13.camel@lenovo.internal.reciva.com \
--to=philb@gnu.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