From: Matthias Scheer <scheer@domain.hid>
To: xenomai@xenomai.org
Subject: [Xenomai-help] Compile-time error with xenomai x86_64 port (probably dualcore related)
Date: Tue, 27 Feb 2007 16:57:58 +0100 [thread overview]
Message-ID: <45E45506.10208@domain.hid> (raw)
[-- Attachment #1: Type: text/plain, Size: 1023 bytes --]
Dear developers,
I'm trying to compile the latest /trunk version together with the adeos
x86_64 patch v1.00.04. The kernel version is 2.6.19.5. The compiling is
done on an Athlon 64 X2 and stops with these error messages:
CC kernel/xenomai/nucleus/pod.o
kernel/xenomai/nucleus/pod.c:944:48: error: macro "cpus_equal" passed 3
arguments, but takes just 2
kernel/xenomai/nucleus/pod.c: In function ‘xnpod_start_thread’:
kernel/xenomai/nucleus/pod.c:944: error: ‘cpus_equal’ undeclared (first
use in this function)
kernel/xenomai/nucleus/pod.c:944: error: (Each undeclared identifier is
reported only once
kernel/xenomai/nucleus/pod.c:944: error: for each function it appears in.)
Notice the _macro "cpus_equal"_ error, which eventually uses the
identifier CPU_MASK_ALL which contains more than one element on a
dualcore system. Does this explanation make sense? And is there a easy
way to fix it? (maybe with a variable number of arguments)
Thanks for your time,
Matthias Scheer
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 6092 bytes --]
next reply other threads:[~2007-02-27 15:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-27 15:57 Matthias Scheer [this message]
2007-02-27 16:06 ` [Xenomai-help] Compile-time error with xenomai x86_64 port (probably dualcore related) Jan Kiszka
2007-02-28 13:40 ` Matthias Scheer
2007-02-28 13:43 ` Jan Kiszka
2007-02-28 13:55 ` Matthias Scheer
2007-02-28 14:36 ` Philippe Gerum
2007-02-28 14:49 ` Matthias Scheer
2007-02-28 15:51 ` Matthias Scheer
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=45E45506.10208@domain.hid \
--to=scheer@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.