From: Wolfgang Grandegger <wg@domain.hid>
To: xenomai-core <xenomai@xenomai.org>
Subject: [Xenomai-core] UVM build error in todays head of SVN
Date: Mon, 01 May 2006 12:32:52 +0200 [thread overview]
Message-ID: <4455E3D4.8060007@domain.hid> (raw)
Hello,
I just checked out Xenomai and realized the UVM build error below (while
building for PPC 405 with IPIPE tracer). "xnlock_put/get" seems not to
be dummy without SMP.
Wolfgang.
if ppc-linux-gcc -DHAVE_CONFIG_H -I. -I. -I../../../../src/include -O2
-D_GNU_SOURCE -D_REENTRANT -D__XENO__ -Wall -pipe -D__IN_XENO__
-Wstrict-prototypes -I../../../../include -D__XENO_UVM__ -MT pod.o
-MD -MP -MF ".deps/pod.Tpo" -c -o pod.o pod.c; \
then mv -f ".deps/pod.Tpo" ".deps/pod.Po"; else rm -f ".deps/pod.Tpo";
exit 1; fi
pod.c: In function 'xnpod_announce_tick':
pod.c:3304: warning: implicit declaration of function 'xnlock_get'
pod.c:3304: error: 'nklock' undeclared (first use in this function)
pod.c:3304: error: (Each undeclared identifier is reported only once
pod.c:3304: error: for each function it appears in.)
pod.c:3365: warning: implicit declaration of function 'xnlock_put'
make[4]: *** [pod.o] Error 1
make[4]: Leaving directory
`/.automount/castor-vlab/root/home/wolf/rt/xenomai/src/skins/uvm/nucleus'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory
`/.automount/castor-vlab/root/home/wolf/rt/xenomai/src/skins/uvm'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory
`/.automount/castor-vlab/root/home/wolf/rt/xenomai/src/skins'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory
`/.automount/castor-vlab/root/home/wolf/rt/xenomai/src'
make: *** [all-recursive] Error 1
next reply other threads:[~2006-05-01 10:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-01 10:32 Wolfgang Grandegger [this message]
2006-05-01 10:46 ` [Xenomai-core] UVM build error in todays head of SVN Jan Kiszka
2006-05-01 13:57 ` Philippe Gerum
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=4455E3D4.8060007@domain.hid \
--to=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.