From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Jan Kiszka <jan.kiszka@domain.hid>
Cc: xenomai-core <xenomai@xenomai.org>
Subject: Re: [Xenomai-core] Commit 6346c046b1
Date: Mon, 06 Jul 2009 18:14:33 +0200 [thread overview]
Message-ID: <4A5222E9.2070105@domain.hid> (raw)
In-Reply-To: <4A4DE69D.1010105@domain.hid>
Jan Kiszka wrote:
> Hi Philippe,
>
> what problem did you had to address with commit 6346c046b1? I'm asking
> as it most probably breaks what e7d889f56c tried to fix (e.g. double
> definitions of PTHREAD_PRIO_* with recent glibcs).
The problem was that with uclibc, pthread_mutexattr_set_prio_inherit
existed, but PTHREAD_PRIO_INHERIT did not exit, so the posix
mutex-torture test was not compiling. Which is why, we replaced with:
#ifndef PTHREAD_PRIO_INHERIT
#define PTHREAD_PRIO_INHERIT
#endif
which should work as long as this piece of code is put after the
#include_next<pthread.h>
But maybe we forgot that...
Besides, I use recent libc (and I believe with -Wall -W) and do not see
any warning . Would you be compiling with g++ or with special flags?
--
Gilles
next prev parent reply other threads:[~2009-07-06 16:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-03 11:08 [Xenomai-core] Commit 6346c046b1 Jan Kiszka
2009-07-06 16:14 ` Gilles Chanteperdrix [this message]
2009-07-06 16:15 ` Gilles Chanteperdrix
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=4A5222E9.2070105@domain.hid \
--to=gilles.chanteperdrix@xenomai.org \
--cc=jan.kiszka@domain.hid \
--cc=xenomai@xenomai.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.