From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: "Charlton, John" <john.charlton@domain.hid>
Cc: "'jan.kiszka@domain.hid'" <jan.kiszka@domain.hid>,
xenomai-core <xenomai@xenomai.org>
Subject: Re: [Xenomai-core] [pull request] Fixes and workarounds for the cond issues
Date: Mon, 08 Mar 2010 19:47:25 +0100 [thread overview]
Message-ID: <4B95463D.2040705@domain.hid> (raw)
In-Reply-To: <CF7FB0793253794F9F45991443E5FE20076A70F4C0@domain.hid>
Charlton, John wrote:
> I configured and built with linux-2.6.32.7 and xenomai-jki for-upstream snapshot: f98569c8eec5df605f806ff58e789668720805ee. I noticed that you removed the PTHREAD_WARNSW so I removed the call to pthread_set_mode_np to remove the following errors:
>
> PosixThread/PosixThread.cpp:1607: error: 'PTHREAD_WARNSW' was not declared in this scope
> PosixThread/PosixThread.cpp:1607: error: 'pthread_set_mode_np' was not declared in this scope
This should come with #include <pthread.h>, provided you use
xeno-config --posix-cflags (soon to be deprecated way)
or xeno-config --skin=posix --cflags
to get the compilation flags.
>
> I am able to run all of my user space application code and unit test
code which uses CanFestival open source CAN library. I am also able to
run the xeno-test which runs to completion with no errors. When I run
the mutex-torture tests I still get the following errors which I have
not looked into in more detail yet:
>
>
> root@domain.hid# ./mutex-torture-native
> simple_wait
> recursive_wait
> timed_mutex
> FAILURE: timed_waiter, waited 4.110 us
> root@domain.hid# ./mutex-torture-posix
> simple_wait
> recursive_wait
> errorcheck_wait
> timed_mutex
> FAILURE: timed_mutex mutex_destroy: 22 (Invalid argument)
>
> I am now looking at xenomai-rpm branch which one is close to 2.5.2 release?
the master branch of the xenomai-2.5 repository. As explained here:
http://www.xenomai.org/index.php/Main_Page
in the "Fetching the source code repositories"
--
Gilles.
next prev parent reply other threads:[~2010-03-08 18:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-02 22:54 [Xenomai-core] [pull request] Fixes and workarounds for the cond issues Jan Kiszka
2010-03-04 10:40 ` Gilles Chanteperdrix
2010-03-04 10:30 ` [Xenomai-core] ADEOS patch for LPC3250 Pierre Ficheux
2010-03-04 13:37 ` Gilles Chanteperdrix
2010-03-04 11:26 ` [Xenomai-core] [pull request] Fixes and workarounds for the cond issues Jan Kiszka
2010-03-04 11:28 ` Jan Kiszka
2010-03-04 13:45 ` Gilles Chanteperdrix
2010-03-04 13:53 ` Jan Kiszka
[not found] ` <CF7FB0793253794F9F45991443E5FE2006483DE99F@us194mx002.tycoelectronics.net>
2010-03-05 18:36 ` Gilles Chanteperdrix
2010-03-08 18:42 ` Charlton, John
2010-03-08 18:47 ` Gilles Chanteperdrix [this message]
2010-03-08 20:39 ` Charlton, John
2010-03-08 20:42 ` Gilles Chanteperdrix
2010-03-08 21:13 ` Charlton, John
2010-03-08 16:32 ` 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=4B95463D.2040705@domain.hid \
--to=gilles.chanteperdrix@xenomai.org \
--cc=jan.kiszka@domain.hid \
--cc=john.charlton@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.