From: Rongqing Li <rongqing.li@windriver.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/1] systemd: ignore qemu output, and check its return code
Date: Wed, 24 Jul 2013 14:15:18 +0800 [thread overview]
Message-ID: <51EF70F6.6060800@windriver.com> (raw)
In-Reply-To: <8651FFE5-8500-4151-A4DF-BE780516C6CC@gmail.com>
On 07/24/2013 01:34 PM, Khem Raj wrote:
>
> On Jul 23, 2013, at 10:24 PM, <rongqing.li@windriver.com> wrote:
>
>> From: "Roy.Li" <rongqing.li@windriver.com>
>>
>> qemu prints errors sometime, but it works well, the error information
>> can be captured by rpm, and lead to rpm failure. like:
>>
>> $export D=/tmp/rootfs;.../usr/bin/qemu-i386 -L $D \
>> -E LD_LIBRARY_PATH=$D/usr/lib:$D/lib $D/bin/udevadm hwdb --update --root $D
>> qemu: Unsupported syscall: 240
>
>
> hmm this is a qemu issue and I bet qemu is segfaulting
> This should be fixed. Can you try porting
>
qemu is not segfaulting, except error message, it returns 0,
and udevadm hwdb finished its task.
> http://lists.gnu.org/archive/html/qemu-devel/2010-02/msg00870.html
>
why was this patch be not merged, it was submitted on 02/2010
-Roy
> To qemu please ?
>
> Then you won't need this patch.
>
>
>
--
Best Reagrds,
Roy | RongQing Li
next prev parent reply other threads:[~2013-07-24 6:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-24 5:24 [PATCH 0/1] systemd: ignore qemu output, and check its return code rongqing.li
2013-07-24 5:24 ` [PATCH 1/1] " rongqing.li
2013-07-24 5:34 ` Khem Raj
2013-07-24 6:15 ` Rongqing Li [this message]
2013-07-26 11:53 ` Burton, Ross
2013-08-05 5:21 ` Rongqing Li
2013-08-07 7:30 ` Rongqing Li
2013-08-07 11:55 ` Burton, Ross
2013-08-08 8:55 ` Rongqing Li
2013-08-08 10:57 ` Burton, Ross
2013-08-07 18:26 ` Khem Raj
2013-08-08 8:53 ` Rongqing Li
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=51EF70F6.6060800@windriver.com \
--to=rongqing.li@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.com \
/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