Re: [Xenomai-help] Problems linking latency

[Philippe Gerum <rpm@xenomai.org>]

Niklaus Giger wrote:
> Hi
> 
> I try to compile Xenomai on my Powerbook for an embedded PPC405. The
> kernel boots okay with the xenomai kernel.
> 
> But when I try to compile the xenomai (trunk) I get the following error:
> 
> »/mnt/data.ng/hcu/kernel/build-xeno-hcu3/src/testsuite/latency«
> /bin/sh ../../../libtool --mode=link --tag=CC powerpc-405-linux-gnu-gcc     -o 
> latency  latency-latency.o ../../skins/native/libnative.la -lpthread -lm
> 
> *** Warning: Linking the executable latency against the loadable module
> *** libnative.so is not portable!
>

Ignore this message, the link is ok anyhow. This will be fixed in later 
releases.

> The Xenomai part of my kernel/.config looks like this
> CONFIG_XENOMAI=y
> CONFIG_XENO_OPT_NUCLEUS=y
> CONFIG_XENO_OPT_PERVASIVE=y
> CONFIG_XENO_OPT_PIPE=y
> CONFIG_XENO_OPT_PIPE_NRDEV=32
> CONFIG_XENO_OPT_SYS_HEAPSZ=128
> # CONFIG_XENO_OPT_ISHIELD is not set
> CONFIG_XENO_OPT_STATS=y
> # CONFIG_XENO_OPT_DEBUG is not set
> # CONFIG_XENO_OPT_WATCHDOG is not set
> # CONFIG_XENO_OPT_SCALABLE_SCHED is not set
> # CONFIG_XENO_HW_FPU is not set
> CONFIG_XENO_HW_PERIODIC_TIMER=y
> CONFIG_XENO_HW_TIMER_LATENCY=0
> CONFIG_XENO_HW_SCHED_LATENCY=0
> CONFIG_XENO_SKIN_NATIVE=m
> CONFIG_XENO_OPT_NATIVE_REGISTRY=y
> CONFIG_XENO_OPT_NATIVE_REGISTRY_NRSLOTS=512
> CONFIG_XENO_OPT_NATIVE_PIPE=y
> CONFIG_XENO_OPT_NATIVE_PIPE_BUFSZ=4096
> CONFIG_XENO_OPT_NATIVE_SEM=y
> CONFIG_XENO_OPT_NATIVE_EVENT=y
> CONFIG_XENO_OPT_NATIVE_MUTEX=y
> CONFIG_XENO_OPT_NATIVE_COND=y
> CONFIG_XENO_OPT_NATIVE_QUEUE=y
> CONFIG_XENO_OPT_NATIVE_HEAP=y
> CONFIG_XENO_OPT_NATIVE_ALARM=y
> CONFIG_XENO_OPT_NATIVE_MPS=y
> CONFIG_XENO_OPT_NATIVE_INTR=y
> # CONFIG_XENO_SKIN_POSIX is not set
> # CONFIG_XENO_SKIN_PSOS is not set
> # CONFIG_XENO_SKIN_UITRON is not set
> # CONFIG_XENO_SKIN_VRTX is not set
> CONFIG_XENO_SKIN_VXWORKS=y
> # CONFIG_XENO_SKIN_RTAI is not set
> # CONFIG_XENO_SKIN_RTDM is not set
> CONFIG_XENO_SKIN_UVM=y
> 
> What is wrong?
> 
> I was also surprised that I could not configure xenomai with 
> CROSS_COMPILE=powerpc-405-linux-gnu- but had do specify
> CC=powerpc-405-linux-gnu-gcc to be able to use the same compiler, with which I 
> built my kernel. 
>

v2.1 stops defining its own set of funky rules for building Xenomai, but 
rather strictly relies on the kernel rules for building kernel support, 
and on the autoconf rules for building user-space support, so it's 
perfectly normal that the new configure script does not recognize 
CROSS_COMPILE since it is a variable defined by Linux's Kbuild system. 
Just follow the appropriate vanilla set of rules depending on which 
support you are trying to build.

> Best regards for any hints.
> 


-- 

Philippe.