Re: [Xenomai-core] Latest snapshot (182) not compiling (kernel)

[Panagiotis Issaris]

Hi Jan,

On 11/28/05, Jan Kiszka <[EMAIL PROTECTED]> wrote:

...
> reference to `__raw_read_unlock'
> kernel/built-in.o: In function `schedule_event':
> /usr/local/src/linux-2.6.14/kernel/xenomai/nucleus/shadow.c:152: undefined
> reference to `__raw_read_lock'
> /usr/local/src/linux-2.6.14/kernel/xenomai/nucleus/shadow.c:158: undefined
> reference to `__raw_read_unlock'
> make[1]: *** [.tmp_vmlinux1] Error 1
> make: *** [_all] Error 2
>

Kernel config...?

Sorry :)

#
# Real-time sub-system
#
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=y
CONFIG_XENO_OPT_STATS=y
# CONFIG_XENO_OPT_DEBUG is not set
# CONFIG_XENO_OPT_WATCHDOG is not set

#
# Scalability
#
# CONFIG_XENO_OPT_SCALABLE_SCHED is not set

#
# Machine
#
CONFIG_XENO_HW_FPU=y
CONFIG_XENO_HW_PERIODIC_TIMER=y
CONFIG_XENO_HW_TIMER_LATENCY=0
CONFIG_XENO_HW_SCHED_LATENCY=0

#
# NMI watchdog
#
# CONFIG_XENO_HW_NMI_DEBUG_LATENCY is not set

#
# SMI workaround
#
# CONFIG_XENO_HW_SMI_DETECT_DISABLE is not set
CONFIG_XENO_HW_SMI_DETECT=y
# CONFIG_XENO_HW_SMI_WORKAROUND is not set

#
# Interfaces
#
CONFIG_XENO_SKIN_NATIVE=y
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=y
# 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 is not set
# CONFIG_XENO_SKIN_RTAI is not set
CONFIG_XENO_SKIN_RTDM=y
# CONFIG_XENO_SKIN_UVM is not set

#
# Drivers
#
# CONFIG_XENO_DRIVERS_16550A is not set


 

Do you happen to have the IRQ shield switched on? May it's a regression
related to this per-default-off feature.

Indeed! I disabled the IRQ shield and the linking error is gone! Thanks! :)


With friendly regards,
Takis