From: Mark Hounschell <dmarkh@cfl.rr.com>
To: Esben Nielsen <nielsen.esben@googlemail.com>
Cc: Ulrich Drepper <drepper@gmail.com>,
linux-kernel@vger.kernel.org, glibc-cvs@sourceware.org
Subject: Re: Where can I get glibc with PI futex support (for -RT tests) ?
Date: Wed, 05 Jul 2006 05:11:51 -0400 [thread overview]
Message-ID: <44AB8257.7000406@cfl.rr.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0607051032070.4248@localhost.localdomain>
Esben Nielsen wrote:
> On Tue, 4 Jul 2006, Ulrich Drepper wrote:
>
>> On 7/4/06, Esben Nielsen <nielsen.esben@googlemail.com> wrote:
>>> The answer is probably on the list, but I can't find it in the
>>> archives..:-(
>>
>> You have to wait your turn like everybody else. Ingo/Thomas have one
>> more bug to fix. After that I'll check in the patches into the cvs
>> archive.
>>
>
> Can I get what you have now? Then I can do some testing.
> I might very well be that the bug doesn't matter for me. What is the bug?
>
> I tried to check out from cvs
> (:pserver:anoncvs@sources.redhat.com:/cvs/glibc) but that can't even
> compile because PTHREAD_MUTEX_PRIO_INHERIT_NP and
> PTHREAD_MUTEX_PRIO_PROTECT_NP isn't defined for pthread_mutex_init.c
>
> Esben
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
Isn't Ingo's patch for glibc-2.4 here?
http://people.redhat.com/mingo/PI-futex-patches/glibc-PI-futex.patch
Builds for me.
Mark
next prev parent reply other threads:[~2006-07-05 9:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-05 0:34 Where can I get glibc with PI futex support (for -RT tests) ? Esben Nielsen
2006-07-05 0:28 ` Ulrich Drepper
2006-07-05 9:34 ` Esben Nielsen
2006-07-05 9:11 ` Mark Hounschell [this message]
2006-07-05 15:58 ` Esben Nielsen
2006-07-05 13:12 ` Dinakar Guniguntala
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=44AB8257.7000406@cfl.rr.com \
--to=dmarkh@cfl.rr.com \
--cc=drepper@gmail.com \
--cc=glibc-cvs@sourceware.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nielsen.esben@googlemail.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 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.