From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Robert Haschke <rhaschke@techfak.uni-bielefeld.de>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai] rtdm_driver.h fails to build: implicit declaration of smp_mb__before_atomic_dec()
Date: Wed, 20 May 2015 02:13:22 +0200 [thread overview]
Message-ID: <20150520001322.GI10686@hermes.click-hack.org> (raw)
In-Reply-To: <555BA2F4.4030106@techfak.uni-bielefeld.de>
On Tue, May 19, 2015 at 10:54:12PM +0200, Robert Haschke wrote:
> I'm trying to build Xenomai 2.6.4 on linux 3.18.13 with i-pipe patch for
> 3.18.12.
> When enabling RTDM support, the compiler throws the following error:
>
> In file included from ../kernel/xenomai/skins/posix/syscall.c:40:0:
> ../include/xenomai/rtdm/rtdm_driver.h: In function ‘rtdm_context_unlock’:
> ../include/xenomai/rtdm/rtdm_driver.h:587:2: error: implicit declaration of
> function ‘smp_mb__before_atomic_dec’ [-Werror=implicit-function-declaration]
> smp_mb__before_atomic_dec();
> ^
> cc1: some warnings being treated as errors
That question again.
Xenomai developers do not have access to a crystal ball or to an
IPOT network. Thus, a released version of Xenomai only supports the
I-pipe patches which were released prior to its release. For this
reason, Xenomai 2.6.4 does not support Linux kernel versions more
recent than 3.14. For more recent releases, use the git repository.
>
> This function became deprecated in kernel 3.16 and was removed in 3.18.
Ah, maybe this explain this commit then:
https://git.xenomai.org/xenomai-2.6.git/commit/?id=d7f7e99ea19eb0dc13b1e02e633ec53ac9b89475
--
Gilles.
next prev parent reply other threads:[~2015-05-20 0:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-19 20:54 [Xenomai] rtdm_driver.h fails to build: implicit declaration of smp_mb__before_atomic_dec() Robert Haschke
2015-05-20 0:13 ` Gilles Chanteperdrix [this message]
2015-05-20 14:37 ` Lennart Sorensen
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=20150520001322.GI10686@hermes.click-hack.org \
--to=gilles.chanteperdrix@xenomai.org \
--cc=rhaschke@techfak.uni-bielefeld.de \
--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.