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

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

[Ignacio García Pérez]

Hi,

I dunno what's changed, but I updated my xenomai snapshot to the latest
revision (182) and the kernel no longer compiles (fails due to some
xnpod_* undefined symbols).

Revision 179 compiled fine.

Nacho.

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

[Panagiotis Issaris]

[-- Attachment #1: Type: text/plain, Size: 2088 bytes --]

Hi,

I'm also having issues compiling the latest Xenomai tree.


On 11/25/05, Ignacio García Pérez <iggarpe@domain.hid > wrote:
>
> Hi,
>
> I dunno what's changed, but I updated my xenomai snapshot to the latest
> revision (182) and the kernel no longer compiles (fails due to some
> xnpod_* undefined symbols).
>
> Revision 179 compiled fine.



I'm using revision 199 on a x86 Ubuntu 5.10 system with GCC 4.0.1 (is anyone
else using that one?).


  LD      init/built-in.o
  LD      .tmp_vmlinux1
kernel/built-in.o: In function `disengage_irq_shield':
/usr/local/src/linux-2.6.14/kernel/xenomai/nucleus/shadow.c:176: undefined
reference to `__raw_write_lock'
/usr/local/src/linux-2.6.14/kernel/xenomai/nucleus/shadow.c:207: undefined
reference to `__raw_write_unlock'
/usr/local/src/linux-2.6.14/kernel/xenomai/nucleus/shadow.c:186: undefined
reference to `__raw_write_unlock'
kernel/built-in.o: In function `xnshadow_reset_shield':
/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'
kernel/built-in.o: In function `lostage_handler':
/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'
kernel/built-in.o: In function `xnshadow_relax':
/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'
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


With friendly regards,
Takis

[-- Attachment #2: Type: text/html, Size: 2620 bytes --]

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

[Jan Kiszka]

[-- Attachment #1: Type: text/plain, Size: 2323 bytes --]

Panagiotis Issaris wrote:
> Hi,
> 
> I'm also having issues compiling the latest Xenomai tree.
> 
> 
> On 11/25/05, Ignacio García Pérez <iggarpe@domain.hid > wrote:
>> Hi,
>>
>> I dunno what's changed, but I updated my xenomai snapshot to the latest
>> revision (182) and the kernel no longer compiles (fails due to some
>> xnpod_* undefined symbols).
>>
>> Revision 179 compiled fine.
> 
> 
> 
> I'm using revision 199 on a x86 Ubuntu 5.10 system with GCC 4.0.1 (is anyone
> else using that one?).
> 
> 
>   LD      init/built-in.o
>   LD      .tmp_vmlinux1
> kernel/built-in.o: In function `disengage_irq_shield':
> /usr/local/src/linux-2.6.14/kernel/xenomai/nucleus/shadow.c:176: undefined
> reference to `__raw_write_lock'
> /usr/local/src/linux-2.6.14/kernel/xenomai/nucleus/shadow.c:207: undefined
> reference to `__raw_write_unlock'
> /usr/local/src/linux-2.6.14/kernel/xenomai/nucleus/shadow.c:186: undefined
> reference to `__raw_write_unlock'
> kernel/built-in.o: In function `xnshadow_reset_shield':
> /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'
> kernel/built-in.o: In function `lostage_handler':
> /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'
> kernel/built-in.o: In function `xnshadow_relax':
> /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'
> 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...?

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

Jan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]

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

[Panagiotis Issaris]

[-- Attachment #1: Type: text/plain, Size: 2316 bytes --]

Hi Jan,

On 11/28/05, Jan Kiszka <kiszka@domain.hid> 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

[-- Attachment #2: Type: text/html, Size: 2942 bytes --]

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

[Philippe Gerum]

Panagiotis Issaris wrote:
> Hi Jan,
> 
> On 11/28/05, *Jan Kiszka* <kiszka@domain.hid 
> <mailto:kiszka@domain.hid>> 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
>      >
> 

ipipe-2.6.14-1.0-11 for x86 and ipipe-2.6.14-1.0-07 for ppc fix this.
Those patches are available from the Xenomai trunk, or from the Adeos dl 
area as usual.

-- 

Philippe.

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

[Philippe Gerum]

Panagiotis Issaris wrote:
> Hi,
> 
> I'm also having issues compiling the latest Xenomai tree.
> 

Mm, dot-config would be great. TIA,

> 
> On 11/25/05, *Ignacio García Pérez* <iggarpe@domain.hid
> <mailto:iggarpe@domain.hid>> wrote:
> 
>     Hi,
> 
>     I dunno what's changed, but I updated my xenomai snapshot to the latest
>     revision (182) and the kernel no longer compiles (fails due to some
>     xnpod_* undefined symbols).
> 
>     Revision 179 compiled fine.
> 
> 
> 
> I'm using revision 199 on a x86 Ubuntu 5.10 system with GCC 4.0.1 (is 
> anyone else using that one?).
> 
> 
>   LD      init/built-in.o
>   LD      .tmp_vmlinux1
> kernel/built-in.o: In function `disengage_irq_shield':
> /usr/local/src/linux-2.6.14/kernel/xenomai/nucleus/shadow.c:176: 
> undefined reference to `__raw_write_lock'
> /usr/local/src/linux-2.6.14/kernel/xenomai/nucleus/shadow.c:207: 
> undefined reference to `__raw_write_unlock'
> /usr/local/src/linux-2.6.14/kernel/xenomai/nucleus/shadow.c:186: 
> undefined reference to `__raw_write_unlock'
> kernel/built-in.o: In function `xnshadow_reset_shield':
> /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'
> kernel/built-in.o: In function `lostage_handler':
> /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'
> kernel/built-in.o: In function `xnshadow_relax':
> /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'
> 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
> 
> 
> With friendly regards,
> Takis
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Xenomai-core mailing list
> Xenomai-core@domain.hid
> https://mail.gna.org/listinfo/xenomai-core


-- 

Philippe.

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

[Panagiotis Issaris]

[-- Attachment #1: Type: text/plain, Size: 412 bytes --]

Hi Philippe,

On 11/28/05, Philippe Gerum <rpm@xenomai.org> wrote:
>
> Panagiotis Issaris wrote:
> > Hi,
> >
> > I'm also having issues compiling the latest Xenomai tree.
> >
>
> Mm, dot-config would be great. TIA,
>
Sorry :)
The problem appears to be gone when disabling the interrupt shield. (An
excerpt from my config can be found in my reply to Jan's e-mail.)

With friendly regards,
Takis

[-- Attachment #2: Type: text/html, Size: 701 bytes --]

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

[Philippe Gerum]

Panagiotis Issaris wrote:
> Hi Philippe,
> 
> On 11/28/05, *Philippe Gerum* <rpm@xenomai.org <mailto:rpm@xenomai.org>> 
> wrote:
> 
>     Panagiotis Issaris wrote:
>      > Hi,
>      >
>      > I'm also having issues compiling the latest Xenomai tree.
>      >
> 
>     Mm, dot-config would be great. TIA,
> 
> Sorry :)
> The problem appears to be gone when disabling the interrupt shield. (An 
> excerpt from my config can be found in my reply to Jan's e-mail.)
>

Confirmed here, there's indeed something fishy. Ok, I will look at this 
asap. Thanks,

> With friendly regards,
> Takis


-- 

Philippe.