From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Wolfgang Grandegger <wg@domain.hid>
Cc: Jan Kiszka <jan.kiszka@domain.hid>, xenomai-core <xenomai@xenomai.org>
Subject: Re: [Xenomai-core] cpu_set_t and friends undefined
Date: Sat, 29 Jul 2006 15:13:17 +0200 [thread overview]
Message-ID: <17611.24301.996280.888596@domain.hid> (raw)
In-Reply-To: <44CB4A1D.1090109@domain.hid>
Wolfgang Grandegger wrote:
> Jan Kiszka wrote:
> > Wolfgang Grandegger wrote:
> >> Hello,
> >>
> >> with todays SVN version of Xenomai, the testsuite program
> >> switchtest/switch.c does not compile because cpu_set_t and friends
> >> (CPU_SET, ...) are not undefined. I'm using kernel version 2.4.25.
> >>
> >> Any idea what goes wrong. I haven't found where cpu_set_t is declared,
> >> not even in Linux 2.4.17.7.
> >
> > That's user-space stuff, in /usr/include/bits/sched.h on my box. Maybe
> > some #ifndef __cpu_set_t_defined + local definition is required here.
> > What glibc version do you use?
>
> Ah, OK. The problem is with gcc version 3.3.3 (DENX ELDK 3.1.1 3.3.3-9),
> which does not have cpu_set_t, indeed. The configure script already
> deals with different implementations of setaffinity. The attached patch
> fixes the problem. It removes CONFIG_SMP, which is not known to user
> space applications anyhow. Well, it might get defined in
> "src/include/xeno_config.h" somehow but I don't know how this could work
> properly without knowing the configured kernel tree.
The configure script has a --enable-smp option that set CONFIG_SMP in
xeno_config.h. sched_setaffinity is unneeded when not running over SMP
machine, so I thought it would be simpler to completely avoid
sched_setaffinity over UP machines.
The proper fix is to also define cpu_set_t when CONFIG_SMP is not set.
I will fix this.
--
Gilles Chanteperdrix.
prev parent reply other threads:[~2006-07-29 13:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-29 9:58 [Xenomai-core] cpu_set_t and friends undefined Wolfgang Grandegger
2006-07-29 10:20 ` Jan Kiszka
2006-07-29 11:44 ` Wolfgang Grandegger
2006-07-29 13:13 ` Gilles Chanteperdrix [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=17611.24301.996280.888596@domain.hid \
--to=gilles.chanteperdrix@xenomai.org \
--cc=jan.kiszka@domain.hid \
--cc=wg@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.