From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Cc: Felipe Contreras <felipe.contreras@gmail.com>
Subject: Re: [Qemu-devel] What happened with NPTL/TLS support?
Date: Mon, 15 Oct 2007 02:06:49 +0100 [thread overview]
Message-ID: <200710150206.50125.paul@codesourcery.com> (raw)
In-Reply-To: <94a0d4530710120812r397d626dvb3044b08e30ebdce@mail.gmail.com>
On Friday 12 October 2007, Felipe Contreras wrote:
> Hi,
>
> When I try to use codesourcery's toolchain arm-2006q3-27 in my Fedora
> 7 box I always have the following issue:
>
> qemu: Unsupported syscall: 983045
>
> I guess it's a problem of NPTL incompatibility. Anyway, the patch that
> Paul Brook sent a while ago solves it [1].
>
> I wonder if it can be integrated or what would be the right way to
> solve this issue. Am I the only one having it?
It needs someone to care enough to make the implementation not suck.
Paul
prev parent reply other threads:[~2007-10-15 1:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-12 15:12 [Qemu-devel] What happened with NPTL/TLS support? Felipe Contreras
2007-10-12 18:22 ` Thayne Harbaugh
2007-10-20 20:34 ` Thiemo Seufer
2007-10-22 14:26 ` Thayne Harbaugh
2007-11-02 13:28 ` Felipe Contreras
2007-11-02 17:06 ` Thayne Harbaugh
2007-10-15 1:06 ` Paul Brook [this message]
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=200710150206.50125.paul@codesourcery.com \
--to=paul@codesourcery.com \
--cc=felipe.contreras@gmail.com \
--cc=qemu-devel@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.