From: Martin Mohring <martin.mohring@opensuse.org>
To: Riku Voipio <riku.voipio@iki.fi>
Cc: qemu-devel@nongnu.org,
"Jan-Simon Möller" <jansimon.moeller@opensuse.org>
Subject: Re: [Qemu-devel] linux-user/arm unsupported syscalls
Date: Wed, 28 Jan 2009 17:36:04 +0100 [thread overview]
Message-ID: <49808974.1080708@opensuse.org> (raw)
In-Reply-To: <200901281728.06882.dl9pf@gmx.de>
Jan-Simon Möller wrote:
> Am Wednesday 28 January 2009 16:22:02 schrieb Riku Voipio:
>
>> On Fri, Jan 23, 2009 at 10:54:09AM +0100, Jan-Simon Möller wrote:
>>
>>>> debian/arm or debian/armel ? Which specific binaries?
>>>>
>>> maemo with some bits of debian/armel
>>>
>> That's hardly "specific binaries", but with my voodoo remote debugging
>> skillz I think I managed to trace this down. The libattr/libacl you are
>> using is missing this patch:
>>
>> http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=5;filename=attr-2.4.32-armel.diff;att=1;bug=421627
>>
>>
>
> Great stuff - i looked into maemo libattr and libacl .
> http://repository.maemo.org/pool/diablo/free/a/acl/
> http://repository.maemo.org/pool/diablo/free/a/attr/
>
> And yes, its missing in attr.
>
> voodoo ;)
>
> skills +1
>
> Best,
> Jan-Simon
Cool. What do you suggest? I could build a new qemu snapshot with that
fixed. Will you consider this for qemu svn inclusion?
Martin
next prev parent reply other threads:[~2009-01-28 16:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-22 19:14 [Qemu-devel] linux-user/arm unsupported syscalls Jan-Simon Möller
2009-01-22 20:37 ` Martin Mohring
2009-01-22 21:04 ` Riku Voipio
2009-01-23 9:54 ` Jan-Simon Möller
2009-01-28 15:22 ` Riku Voipio
2009-01-28 16:28 ` Jan-Simon Möller
2009-01-28 16:36 ` Martin Mohring [this message]
2009-01-28 16:46 ` Riku Voipio
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=49808974.1080708@opensuse.org \
--to=martin.mohring@opensuse.org \
--cc=jansimon.moeller@opensuse.org \
--cc=qemu-devel@nongnu.org \
--cc=riku.voipio@iki.fi \
/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;
as well as URLs for NNTP newsgroup(s).