All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Galea <michaelgalea@domain.hid>
To: xenomai@xenomai.org
Subject: Re: [Xenomai-help] Xenomai kernel user-space problem running testsuite
Date: Fri, 08 Aug 2008 16:58:16 -0400	[thread overview]
Message-ID: <489CB368.8030108@domain.hid> (raw)
In-Reply-To: <489CA27B.1040201@domain.hid>

Philippe Gerum wrote:
> Michael Galea wrote:
>> I'm just starting with xenomai and am having troubles getting xenomai 
>> user space to talk to my kernel.
>>
>> I build the kernel and user-space xenomai code and try to run `latency` 
>> from the test suite and get
>> mpc8360mds:# /usr/local/xenomai/bin/latency
>> Xenomai: incompatible feature set
>> (required="fastsem", present="nofastsem", missing="fastsem").
>>
>>
>> I have built xenomai from svn into my 2.6.26 powerpc kernel and it looks 
>>   good on the next boot, i.e. `dmesg |grep xeno -i` returns:
>> I-pipe: Domain Xenomai registered.
>> Xenomai: hal/powerpc started.
>> Xenomai: real-time nucleus v2.5-devel (Flying In A Blue Dream) loaded.
>> Xenomai: starting native API services.
>> Xenomai: starting POSIX services.
>> Xenomai: starting RTDM services.
>>
>> The user-space builds and installs over NFS just fine:
>>
>> ./configure --host=ppc-unknown-linux-gnu --prefix=/usr/local/xenomai \
>>    CC=ppc_6xx-gcc CXX=ppc_6xx-g++ LD=ppc_6xx-ld
>> make
>> make DESTDIR=/opt/ppcrootmds/ install
>>
>>
>> I can't see any fastsem options in the kernel.  Does anyone have any 
>> advice?
> 
> The trunk/ contains bleeding edge code. The powerpc port there is currently in a
> state of flux, due to the introduction of fast user-space mutexes in the Xenomai
> nucleus.
> 
> Please use the latest stable version such as 2.4.4, or our maintenance branch
> instead: http://svn.gna.org/viewcvs/xenomai/branches/v2.4.x/.
> 
Hi Phillipe,
	In trying to build xenomai 2.4.4 into the 2.6.26 kernel, using the 
default kconfig, I get

   CC      kernel/xenomai/arch/generic/hal.o
   LD      kernel/xenomai/arch/generic/xeno_hal.o
   LD      kernel/xenomai/arch/generic/built-in.o
   LD      kernel/xenomai/arch/built-in.o
   CC      kernel/xenomai/nucleus/heap.o
kernel/xenomai/nucleus/heap.c: In function 'xnheap_mount':
kernel/xenomai/nucleus/heap.c:1140: error: implicit declaration of 
function 'class_device_create'
kernel/xenomai/nucleus/heap.c:1142: warning: assignment makes pointer 
from integer without a cast
kernel/xenomai/nucleus/heap.c: In function 'xnheap_umount':
kernel/xenomai/nucleus/heap.c:1160: error: implicit declaration of 
function 'class_device_destroy'
make[3]: *** [kernel/xenomai/nucleus/heap.o] Error 1
make[2]: *** [kernel/xenomai/nucleus] Error 2
make[1]: *** [kernel/xenomai] Error 2
make: *** [kernel] Error 2

You mentioned the maintenance branch, where can I find that?

-- 
Michael Galea
30 Whitmore Road
Woodbridge, Ontario, Canada, L4L 7Z4
Ph: (905) 266-1745
Fx: (905) 856-1995
www.ruggedcom.com




  reply	other threads:[~2008-08-08 20:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-08 18:56 [Xenomai-help] Xenomai kernel user-space problem running testsuite Michael Galea
2008-08-08 19:46 ` Philippe Gerum
2008-08-08 20:58   ` Michael Galea [this message]
2008-08-08 21:17     ` Philippe Gerum
2008-08-08 20:38 ` Gilles Chanteperdrix
2008-08-09 13:37 ` Wolfgang Grandegger

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=489CB368.8030108@domain.hid \
    --to=michaelgalea@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.