[Xenomai-help] Usage of sim with xenomai-2.0

[Xenomai-help] Usage of sim with xenomai-2.0

[ROSSIER Daniel]

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

Hi xeno-workers,

 

I'm trying to compile the simulator of xenomai-2.0 within a kernel 2.6.9 but I get

the following error when gcc-2.95.3 is being compiled: "/usr/include/bits/stdio-lock.h:24: lowlevellock.h: No such file or directory"

(I presume that this include is not supported anymore by my current libc)

 

I'm pretty sure that it is not a new issue - Sorry about this - I probably missed the workaround.

Please, would you be so kind as to help me?

 

Thanks in advance

 

Cheers

Daniel

 

 

 

 

Dr. Daniel Rossier, Professeur

REDS, Reconfigurable & Embedded Digital Systems, http://reds.eivd.ch/ <http://reds.eivd.ch/> 

HES-SO

Haute Ecole d'Ingénieurs et de Gestion (HEIG-VD)

Rte de Cheseaux 1

 

CH-1774 Yverdon-les-Bains

 

Tél. fixe:     +41 24 557 62 69

Tél. mobile:   +41 79 292 54 58

E-mail:        daniel.rossier@domain.hid

 


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

Re: [Xenomai-help] Usage of sim with xenomai-2.0

[Philippe Gerum]

ROSSIER Daniel wrote:
> Hi xeno-workers,
> 
>  
> 
> I'm trying to compile the simulator of xenomai-2.0 within a kernel 2.6.9 
> but I get
> 
> the following error when gcc-2.95.3 is being compiled: 
> "/usr/include/bits/stdio-lock.h:24: lowlevellock.h: No such file or 
> directory"
> 
> (I presume that this include is not supported anymore by my current libc)
> 
>  
> 
> I'm pretty sure that it is not a new issue - Sorry about this - I 
> probably missed the workaround.
> 

This one is new actually. Could you send more information about your environment 
(glibc version, distro, compiler version) and the fragment of the output log 
containing the error message? TIA,

> Please, would you be so kind as to help me?
> 
>  
> 
> Thanks in advance
> 
>  
> 
> Cheers
> 
> Daniel
> 
>  
> 
>  
> 
>  
> 
>  
> 
> Dr. Daniel Rossier, Professeur
> 
> REDS, Reconfigurable & Embedded Digital Systems, http://reds.eivd.ch/
> 
> HES-SO
> 
> Haute Ecole d'Ingénieurs et de Gestion (HEIG-VD)
> 
> Rte de Cheseaux 1
> 
>  
> 
> CH-1774 Yverdon-les-Bains
> 
>  
> 
> Tél. fixe:     +41 24 557 62 69
> 
> Tél. mobile:   +41 79 292 54 58
> 
> E-mail:        daniel.rossier@domain.hid <mailto:daniel.rossier@domain.hid.ch>
> 
>  
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Xenomai-help mailing list
> Xenomai-help@domain.hid
> https://mail.gna.org/listinfo/xenomai-help


-- 

Philippe.

RE: [Xenomai-help] Usage of sim with xenomai-2.0

[ROSSIER Daniel]

Hi Philippe,

Here is the info about my env:

- kernel 2.6.9
- glibc 2.3.5
- gcc 3.4.4
- actually, I built my env. from scratch (no distro) - simply from www.linuxfromscratch.org

But everything else works fine :-) (xenomai works perfectly. I tested it with the LinuxTraceToolkit, and it works as well)

Here is the fragment of log, right before the failure (all the compilation steps before are OK):


make[4]: Leaving directory `/home/rossier/xenomai-2.0/sim/gcic/gcc-build/i686-pc-linux-gnu/libiberty'
make[3]: Leaving directory `/home/rossier/xenomai-2.0/sim/gcic/gcc-build/i686-pc-linux-gnu/libiberty'
make[3]: Entering directory `/home/rossier/xenomai-2.0/sim/gcic/gcc-build/i686-pc-linux-gnu/libio'
if [ x"no" = xyes ] && [ ! -d pic ]; then \
  mkdir pic; \
else true; fi
touch stamp-picdir
test x"no" != xyes ||\
  /home/rossier/xenomai-2.0/sim/gcic/gcc-build/gcc/xgcc -B/home/rossier/xenomai-2.0/sim/gcic/gcc-build/gcc/ -B/usr/realtime/libexec/gcic/i686-pc-linux-gnu/bin/ -c -g -O2 -I. -I../../../gcc-2.95.3/libio -D_IO_MTSAFE_IO  ../../../gcc-2.95.3/libio/iogetline.c -o pic/iogetline.o /home/rossier/xenomai-2.0/sim/gcic/gcc-build/gcc/xgcc -B/home/rossier/xenomai-2.0/sim/gcic/gcc-build/gcc/ -B/usr/realtime/libexec/gcic/i686-pc-linux-gnu/bin/ -c -g -O2 -I. -I../../../gcc-2.95.3/libio -D_IO_MTSAFE_IO ../../../gcc-2.95.3/libio/iogetline.c
In file included from ../../../gcc-2.95.3/libio/libio.h:167,
                 from ../../../gcc-2.95.3/libio/iolibio.h:1,
                 from ../../../gcc-2.95.3/libio/libioP.h:47,
                 from ../../../gcc-2.95.3/libio/iogetline.c:26:
/usr/include/bits/stdio-lock.h:24: lowlevellock.h: No such file or directory
make[3]: *** [iogetline.o] Error 1
make[3]: Leaving directory `/home/rossier/xenomai-2.0/sim/gcic/gcc-build/i686-pc-linux-gnu/libio'
make[2]: *** [all-target-libio] Error 2
make[2]: Leaving directory `/home/rossier/xenomai-2.0/sim/gcic/gcc-build'
make[1]: *** [gcc-build/.gcic-built] Error 2
make[1]: Leaving directory `/home/rossier/xenomai-2.0/sim/gcic'
make: *** [all-recursive] Error 1
root@domain.hid#


Thanks a lot.

Cheers

Daniel



-----Message d'origine-----
De : Philippe Gerum [mailto:rpm@xenomai.org
Envoyé : mardi, 25. octobre 2005 15:03
À : ROSSIER Daniel
Cc : xenomai@xenomai.org
Objet : Re: [Xenomai-help] Usage of sim with xenomai-2.0

ROSSIER Daniel wrote:
> Hi xeno-workers,
> 
>  
> 
> I'm trying to compile the simulator of xenomai-2.0 within a kernel 2.6.9 
> but I get
> 
> the following error when gcc-2.95.3 is being compiled: 
> "/usr/include/bits/stdio-lock.h:24: lowlevellock.h: No such file or 
> directory"
> 
> (I presume that this include is not supported anymore by my current libc)
> 
>  
> 
> I'm pretty sure that it is not a new issue - Sorry about this - I 
> probably missed the workaround.
> 

This one is new actually. Could you send more information about your environment 
(glibc version, distro, compiler version) and the fragment of the output log 
containing the error message? TIA,

> Please, would you be so kind as to help me?
> 
>  
> 
> Thanks in advance
> 
>  
> 
> Cheers
> 
> Daniel
> 
>  
> 
>  
> 
>  
> 
>  
> 
> Dr. Daniel Rossier, Professeur
> 
> REDS, Reconfigurable & Embedded Digital Systems, http://reds.eivd.ch/
> 
> HES-SO
> 
> Haute Ecole d'Ingénieurs et de Gestion (HEIG-VD)
> 
> Rte de Cheseaux 1
> 
>  
> 
> CH-1774 Yverdon-les-Bains
> 
>  
> 
> Tél. fixe:     +41 24 557 62 69
> 
> Tél. mobile:   +41 79 292 54 58
> 
> E-mail:        daniel.rossier@domain.hid <mailto:daniel.rossier@domain.hid>
> 
>  
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Xenomai-help mailing list
> Xenomai-help@domain.hid
> https://mail.gna.org/listinfo/xenomai-help


-- 

Philippe.

Re: [Xenomai-help] Usage of sim with xenomai-2.0

[Philippe Gerum]

ROSSIER Daniel wrote:
> Hi Philippe,
> 
> Here is the info about my env:
> 
> - kernel 2.6.9
> - glibc 2.3.5
> - gcc 3.4.4
> - actually, I built my env. from scratch (no distro) - simply from www.linuxfromscratch.org
> 
> But everything else works fine :-) (xenomai works perfectly. I tested it with the LinuxTraceToolkit, and it works as well)
> 
> Here is the fragment of log, right before the failure (all the compilation steps before are OK):
> 
> 
> make[4]: Leaving directory `/home/rossier/xenomai-2.0/sim/gcic/gcc-build/i686-pc-linux-gnu/libiberty'
> make[3]: Leaving directory `/home/rossier/xenomai-2.0/sim/gcic/gcc-build/i686-pc-linux-gnu/libiberty'
> make[3]: Entering directory `/home/rossier/xenomai-2.0/sim/gcic/gcc-build/i686-pc-linux-gnu/libio'
> if [ x"no" = xyes ] && [ ! -d pic ]; then \
>   mkdir pic; \
> else true; fi
> touch stamp-picdir
> test x"no" != xyes ||\
>   /home/rossier/xenomai-2.0/sim/gcic/gcc-build/gcc/xgcc -B/home/rossier/xenomai-2.0/sim/gcic/gcc-build/gcc/ -B/usr/realtime/libexec/gcic/i686-pc-linux-gnu/bin/ -c -g -O2 -I. -I../../../gcc-2.95.3/libio -D_IO_MTSAFE_IO  ../../../gcc-2.95.3/libio/iogetline.c -o pic/iogetline.o /home/rossier/xenomai-2.0/sim/gcic/gcc-build/gcc/xgcc -B/home/rossier/xenomai-2.0/sim/gcic/gcc-build/gcc/ -B/usr/realtime/libexec/gcic/i686-pc-linux-gnu/bin/ -c -g -O2 -I. -I../../../gcc-2.95.3/libio -D_IO_MTSAFE_IO ../../../gcc-2.95.3/libio/iogetline.c
> In file included from ../../../gcc-2.95.3/libio/libio.h:167,
>                  from ../../../gcc-2.95.3/libio/iolibio.h:1,
>                  from ../../../gcc-2.95.3/libio/libioP.h:47,
>                  from ../../../gcc-2.95.3/libio/iogetline.c:26:
> /usr/include/bits/stdio-lock.h:24: lowlevellock.h: No such file or directory
> make[3]: *** [iogetline.o] Error 1
> make[3]: Leaving directory `/home/rossier/xenomai-2.0/sim/gcic/gcc-build/i686-pc-linux-gnu/libio'
> make[2]: *** [all-target-libio] Error 2
> make[2]: Leaving directory `/home/rossier/xenomai-2.0/sim/gcic/gcc-build'
> make[1]: *** [gcc-build/.gcic-built] Error 2
> make[1]: Leaving directory `/home/rossier/xenomai-2.0/sim/gcic'
> make: *** [all-recursive] Error 1
> root@domain.hid#
> 

It seems to be an incompatibility issue between the NPTL and gcc-2.95.x:
http://sources.redhat.com/ml/glibc-bugs/2004-06/msg00144.html

The best way to solve this would be to get rid of the MT support for building 
the GCC-based instrumenter, since we don't need it, and libio/ compilation would 
not break. I'll look at some way to fix this.

> 
> Thanks a lot.
> 
> Cheers
> 
> Daniel
> 
> 
> 
> -----Message d'origine-----
> De : Philippe Gerum [mailto:rpm@xenomai.org
> Envoyé : mardi, 25. octobre 2005 15:03
> À : ROSSIER Daniel
> Cc : xenomai@xenomai.org
> Objet : Re: [Xenomai-help] Usage of sim with xenomai-2.0
> 
> ROSSIER Daniel wrote:
> 
>>Hi xeno-workers,
>>
>> 
>>
>>I'm trying to compile the simulator of xenomai-2.0 within a kernel 2.6.9 
>>but I get
>>
>>the following error when gcc-2.95.3 is being compiled: 
>>"/usr/include/bits/stdio-lock.h:24: lowlevellock.h: No such file or 
>>directory"
>>
>>(I presume that this include is not supported anymore by my current libc)
>>
>> 
>>
>>I'm pretty sure that it is not a new issue - Sorry about this - I 
>>probably missed the workaround.
>>
> 
> 
> This one is new actually. Could you send more information about your environment 
> (glibc version, distro, compiler version) and the fragment of the output log 
> containing the error message? TIA,
> 
> 
>>Please, would you be so kind as to help me?
>>
>> 
>>
>>Thanks in advance
>>
>> 
>>
>>Cheers
>>
>>Daniel
>>
>> 
>>
>> 
>>
>> 
>>
>> 
>>
>>Dr. Daniel Rossier, Professeur
>>
>>REDS, Reconfigurable & Embedded Digital Systems, http://reds.eivd.ch/
>>
>>HES-SO
>>
>>Haute Ecole d'Ingénieurs et de Gestion (HEIG-VD)
>>
>>Rte de Cheseaux 1
>>
>> 
>>
>>CH-1774 Yverdon-les-Bains
>>
>> 
>>
>>Tél. fixe:     +41 24 557 62 69
>>
>>Tél. mobile:   +41 79 292 54 58
>>
>>E-mail:        daniel.rossier@domain.hid <mailto:daniel.rossier@domain.hid.ch>
>>
>> 
>>
>>
>>------------------------------------------------------------------------
>>
>>_______________________________________________
>>Xenomai-help mailing list
>>Xenomai-help@domain.hid
>>https://mail.gna.org/listinfo/xenomai-help
> 
> 
> 


-- 

Philippe.

RE: [Xenomai-help] Usage of sim with xenomai-2.0

[ROSSIER Daniel]

Ok, I will also try to have a look. Maybe, an idea would be to migrate to gcc-3.4.4 for the code
instrumentation...Are there specific issues related to the gcc version for that?

Daniel


-----Original Message-----
From: Philippe Gerum [mailto:rpm@xenomai.org]
Sent: Tue 10/25/2005 4:00 PM
To: ROSSIER Daniel
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] Usage of sim with xenomai-2.0
 
ROSSIER Daniel wrote:
> Hi Philippe,
> 
> Here is the info about my env:
> 
> - kernel 2.6.9
> - glibc 2.3.5
> - gcc 3.4.4
> - actually, I built my env. from scratch (no distro) - simply from www.linuxfromscratch.org
> 
> But everything else works fine :-) (xenomai works perfectly. I tested it with the LinuxTraceToolkit, and it works as well)
> 
> Here is the fragment of log, right before the failure (all the compilation steps before are OK):
> 
> 
> make[4]: Leaving directory `/home/rossier/xenomai-2.0/sim/gcic/gcc-build/i686-pc-linux-gnu/libiberty'
> make[3]: Leaving directory `/home/rossier/xenomai-2.0/sim/gcic/gcc-build/i686-pc-linux-gnu/libiberty'
> make[3]: Entering directory `/home/rossier/xenomai-2.0/sim/gcic/gcc-build/i686-pc-linux-gnu/libio'
> if [ x"no" = xyes ] && [ ! -d pic ]; then \
>   mkdir pic; \
> else true; fi
> touch stamp-picdir
> test x"no" != xyes ||\
>   /home/rossier/xenomai-2.0/sim/gcic/gcc-build/gcc/xgcc -B/home/rossier/xenomai-2.0/sim/gcic/gcc-build/gcc/ -B/usr/realtime/libexec/gcic/i686-pc-linux-gnu/bin/ -c -g -O2 -I. -I../../../gcc-2.95.3/libio -D_IO_MTSAFE_IO  ../../../gcc-2.95.3/libio/iogetline.c -o pic/iogetline.o /home/rossier/xenomai-2.0/sim/gcic/gcc-build/gcc/xgcc -B/home/rossier/xenomai-2.0/sim/gcic/gcc-build/gcc/ -B/usr/realtime/libexec/gcic/i686-pc-linux-gnu/bin/ -c -g -O2 -I. -I../../../gcc-2.95.3/libio -D_IO_MTSAFE_IO ../../../gcc-2.95.3/libio/iogetline.c
> In file included from ../../../gcc-2.95.3/libio/libio.h:167,
>                  from ../../../gcc-2.95.3/libio/iolibio.h:1,
>                  from ../../../gcc-2.95.3/libio/libioP.h:47,
>                  from ../../../gcc-2.95.3/libio/iogetline.c:26:
> /usr/include/bits/stdio-lock.h:24: lowlevellock.h: No such file or directory
> make[3]: *** [iogetline.o] Error 1
> make[3]: Leaving directory `/home/rossier/xenomai-2.0/sim/gcic/gcc-build/i686-pc-linux-gnu/libio'
> make[2]: *** [all-target-libio] Error 2
> make[2]: Leaving directory `/home/rossier/xenomai-2.0/sim/gcic/gcc-build'
> make[1]: *** [gcc-build/.gcic-built] Error 2
> make[1]: Leaving directory `/home/rossier/xenomai-2.0/sim/gcic'
> make: *** [all-recursive] Error 1
> root@domain.hid#
> 

It seems to be an incompatibility issue between the NPTL and gcc-2.95.x:
http://sources.redhat.com/ml/glibc-bugs/2004-06/msg00144.html

The best way to solve this would be to get rid of the MT support for building 
the GCC-based instrumenter, since we don't need it, and libio/ compilation would 
not break. I'll look at some way to fix this.

> 
> Thanks a lot.
> 
> Cheers
> 
> Daniel
> 
> 
> 
> -----Message d'origine-----
> De : Philippe Gerum [mailto:rpm@xenomai.org
> Envoyé : mardi, 25. octobre 2005 15:03
> À : ROSSIER Daniel
> Cc : xenomai@xenomai.org
> Objet : Re: [Xenomai-help] Usage of sim with xenomai-2.0
> 
> ROSSIER Daniel wrote:
> 
>>Hi xeno-workers,
>>
>> 
>>
>>I'm trying to compile the simulator of xenomai-2.0 within a kernel 2.6.9 
>>but I get
>>
>>the following error when gcc-2.95.3 is being compiled: 
>>"/usr/include/bits/stdio-lock.h:24: lowlevellock.h: No such file or 
>>directory"
>>
>>(I presume that this include is not supported anymore by my current libc)
>>
>> 
>>
>>I'm pretty sure that it is not a new issue - Sorry about this - I 
>>probably missed the workaround.
>>
> 
> 
> This one is new actually. Could you send more information about your environment 
> (glibc version, distro, compiler version) and the fragment of the output log 
> containing the error message? TIA,
> 
> 
>>Please, would you be so kind as to help me?
>>
>> 
>>
>>Thanks in advance
>>
>> 
>>
>>Cheers
>>
>>Daniel
>>
>> 
>>
>> 
>>
>> 
>>
>> 
>>
>>Dr. Daniel Rossier, Professeur
>>
>>REDS, Reconfigurable & Embedded Digital Systems, http://reds.eivd.ch/
>>
>>HES-SO
>>
>>Haute Ecole d'Ingénieurs et de Gestion (HEIG-VD)
>>
>>Rte de Cheseaux 1
>>
>> 
>>
>>CH-1774 Yverdon-les-Bains
>>
>> 
>>
>>Tél. fixe:     +41 24 557 62 69
>>
>>Tél. mobile:   +41 79 292 54 58
>>
>>E-mail:        daniel.rossier@domain.hid <mailto:daniel.rossier@domain.hid>
>>
>> 
>>
>>
>>------------------------------------------------------------------------
>>
>>_______________________________________________
>>Xenomai-help mailing list
>>Xenomai-help@domain.hid
>>https://mail.gna.org/listinfo/xenomai-help
> 
> 
> 


-- 

Philippe.

Re: [Xenomai-help] Usage of sim with xenomai-2.0

[Philippe Gerum]

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

Philippe Gerum wrote:
> ROSSIER Daniel wrote:
> 
>> Hi Philippe,
>>
>> Here is the info about my env:
>>
>> - kernel 2.6.9
>> - glibc 2.3.5
>> - gcc 3.4.4
>> - actually, I built my env. from scratch (no distro) - simply from 
>> www.linuxfromscratch.org
>>
>> But everything else works fine :-) (xenomai works perfectly. I tested 
>> it with the LinuxTraceToolkit, and it works as well)
>>
>> Here is the fragment of log, right before the failure (all the 
>> compilation steps before are OK):
>>
>>
>> make[4]: Leaving directory 
>> `/home/rossier/xenomai-2.0/sim/gcic/gcc-build/i686-pc-linux-gnu/libiberty' 
>>
>> make[3]: Leaving directory 
>> `/home/rossier/xenomai-2.0/sim/gcic/gcc-build/i686-pc-linux-gnu/libiberty' 
>>
>> make[3]: Entering directory 
>> `/home/rossier/xenomai-2.0/sim/gcic/gcc-build/i686-pc-linux-gnu/libio'
>> if [ x"no" = xyes ] && [ ! -d pic ]; then \
>>   mkdir pic; \
>> else true; fi
>> touch stamp-picdir
>> test x"no" != xyes ||\
>>   /home/rossier/xenomai-2.0/sim/gcic/gcc-build/gcc/xgcc 
>> -B/home/rossier/xenomai-2.0/sim/gcic/gcc-build/gcc/ 
>> -B/usr/realtime/libexec/gcic/i686-pc-linux-gnu/bin/ -c -g -O2 -I. 
>> -I../../../gcc-2.95.3/libio -D_IO_MTSAFE_IO  
>> ../../../gcc-2.95.3/libio/iogetline.c -o pic/iogetline.o 
>> /home/rossier/xenomai-2.0/sim/gcic/gcc-build/gcc/xgcc 
>> -B/home/rossier/xenomai-2.0/sim/gcic/gcc-build/gcc/ 
>> -B/usr/realtime/libexec/gcic/i686-pc-linux-gnu/bin/ -c -g -O2 -I. 
>> -I../../../gcc-2.95.3/libio -D_IO_MTSAFE_IO 
>> ../../../gcc-2.95.3/libio/iogetline.c
>> In file included from ../../../gcc-2.95.3/libio/libio.h:167,
>>                  from ../../../gcc-2.95.3/libio/iolibio.h:1,
>>                  from ../../../gcc-2.95.3/libio/libioP.h:47,
>>                  from ../../../gcc-2.95.3/libio/iogetline.c:26:
>> /usr/include/bits/stdio-lock.h:24: lowlevellock.h: No such file or 
>> directory
>> make[3]: *** [iogetline.o] Error 1
>> make[3]: Leaving directory 
>> `/home/rossier/xenomai-2.0/sim/gcic/gcc-build/i686-pc-linux-gnu/libio'
>> make[2]: *** [all-target-libio] Error 2
>> make[2]: Leaving directory `/home/rossier/xenomai-2.0/sim/gcic/gcc-build'
>> make[1]: *** [gcc-build/.gcic-built] Error 2
>> make[1]: Leaving directory `/home/rossier/xenomai-2.0/sim/gcic'
>> make: *** [all-recursive] Error 1
>> root@domain.hid#
>>
> 
> It seems to be an incompatibility issue between the NPTL and gcc-2.95.x:
> http://sources.redhat.com/ml/glibc-bugs/2004-06/msg00144.html
> 
> The best way to solve this would be to get rid of the MT support for 
> building the GCC-based instrumenter, since we don't need it, and libio/ 
> compilation would not break. I'll look at some way to fix this.
> 

Could you try the following steps and let me know if that works in your environment:

- unpack the gcc-2.95.3 archive
- apply the attached patch against the gcc tree
- pack back the tree
- configure, build and install Xenomai again to use the patched gcc archive for 
building the simulator.

In order to test the resulting stuff:

- export PATH=/usr/realtime/bin:$PATH
- export LD_LIBRARY_PATH=/usr/realtime/lib:$LD_LIBRARY_PATH
- cd xenomai-2.0/skins/vxworks/demos
- make sim

You should have the "satch_s" executable available in the current dir at that 
point; just start the following command then:
$ xenoscope satch_s

PS: at Xenomai configuration time, make sure to have selected the VxWorks skin 
among the APIs to build.

-- 

Philippe.

[-- Attachment #2: gcc-2.95.3-no-mt.patch --]
[-- Type: text/x-patch, Size: 740 bytes --]

diff -uNrp gcc-2.95.3/libio/config/mtsafe.mt gcc-2.95.3-no-mt/libio/config/mtsafe.mt
--- gcc-2.95.3/libio/config/mtsafe.mt	1997-09-27 06:07:24.000000000 +0200
+++ gcc-2.95.3-no-mt/libio/config/mtsafe.mt	2005-10-25 19:43:24.000000000 +0200
@@ -1,2 +1,3 @@
 # tell we want the mt-safe version
-MT_CFLAGS = -D_IO_MTSAFE_IO
+# MT_CFLAGS = -D_IO_MTSAFE_IO
+MT_CFLAGS =
diff -uNrp gcc-2.95.3/libstdc++/config/linux.mt gcc-2.95.3-no-mt/libstdc++/config/linux.mt
--- gcc-2.95.3/libstdc++/config/linux.mt	1998-02-01 13:38:27.000000000 +0100
+++ gcc-2.95.3-no-mt/libstdc++/config/linux.mt	2005-10-25 19:43:07.000000000 +0200
@@ -1,2 +1,3 @@
 # tell we want the mt-safe version
-MT_CFLAGS = -D_IO_MTSAFE_IO
+# MT_CFLAGS = -D_IO_MTSAFE_IO
+MT_CFLAGS =

RE: [Xenomai-help] Usage of sim with xenomai-2.0

[ROSSIER Daniel]

Well, I applied the patch and I was hopeful when it compiled the libio stuff. Unfortunately, the following error came out after a while:

/home/rossier/xenomai-2.0/sim/gcic/gcc-build/gcc/xgcc -B/home/rossier/xenomai-2.0/sim/gcic/gcc-build/gcc/ -B/usr/realtime/libexec/gcic/i686-pc-linux-gnu/bin/ -c -g -O2 -fvtable-thunks -D_GNU_SOURCE -fno-implicit-templates -I../../../gcc-2.95.3/libstdc++ -I../../../gcc-2.95.3/libstdc++/stl -I../libio -I../../../gcc-2.95.3/libstdc++/../libio -nostdinc++   ../../../gcc-2.95.3/libstdc++/stlinst.cc -o pic/stlinst.o
/home/rossier/xenomai-2.0/sim/gcic/gcc-build/gcc/xgcc -B/home/rossier/xenomai-2.0/sim/gcic/gcc-build/gcc/ -B/usr/realtime/libexec/gcic/i686-pc-linux-gnu/bin/ -c -g -O2 -fvtable-thunks -D_GNU_SOURCE -fno-implicit-templates -I../../../gcc-2.95.3/libstdc++ -I../../../gcc-2.95.3/libstdc++/stl -I../libio -I../../../gcc-2.95.3/libstdc++/../libio -nostdinc++  ../../../gcc-2.95.3/libstdc++/stlinst.cc
../../../gcc-2.95.3/libstdc++/stl/stl_alloc.h: In instantiation of `__default_alloc_template<true,0>::_S_node_allocator_lock':
../../../gcc-2.95.3/libstdc++/stl/stl_alloc.h:394:   instantiated from `__default_alloc_template<true,0>::_Lock::~_Lock()'
../../../gcc-2.95.3/libstdc++/stl/stl_alloc.h:415:   instantiated from `__default_alloc_template<true,0>::allocate(unsigned int)'
../../../gcc-2.95.3/libstdc++/stlinst.cc:7:   instantiated from here
../../../gcc-2.95.3/libstdc++/stl/stl_alloc.h:581: Internal compiler error.
../../../gcc-2.95.3/libstdc++/stl/stl_alloc.h:581: Please submit a full bug report.
../../../gcc-2.95.3/libstdc++/stl/stl_alloc.h:581: See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions.
make[2]: *** [stlinst.o] Error 1
make[2]: Leaving directory `/home/rossier/xenomai-2.0/sim/gcic/gcc-build/i686-pc-linux-gnu/libstdc++'
make[1]: *** [all-target-libstdc++] Error 2
make[1]: Leaving directory `/home/rossier/xenomai-2.0/sim/gcic/gcc-build'
make: *** [gcc-build/.gcic-built] Error 2
root@domain.hid#  


'sounds bad :-(  No idea what it can be. Do you have an idea?


Daniel



-----Original Message-----
From: Philippe Gerum [mailto:rpm@xenomai.org]
Sent: Tue 10/25/2005 8:29 PM
To: Philippe Gerum
Cc: ROSSIER Daniel; xenomai@xenomai.org
Subject: Re: [Xenomai-help] Usage of sim with xenomai-2.0
 
Philippe Gerum wrote:
> ROSSIER Daniel wrote:
> 
>> Hi Philippe,
>>
>> Here is the info about my env:
>>
>> - kernel 2.6.9
>> - glibc 2.3.5
>> - gcc 3.4.4
>> - actually, I built my env. from scratch (no distro) - simply from 
>> www.linuxfromscratch.org
>>
>> But everything else works fine :-) (xenomai works perfectly. I tested 
>> it with the LinuxTraceToolkit, and it works as well)
>>
>> Here is the fragment of log, right before the failure (all the 
>> compilation steps before are OK):
>>
>>
>> make[4]: Leaving directory 
>> `/home/rossier/xenomai-2.0/sim/gcic/gcc-build/i686-pc-linux-gnu/libiberty' 
>>
>> make[3]: Leaving directory 
>> `/home/rossier/xenomai-2.0/sim/gcic/gcc-build/i686-pc-linux-gnu/libiberty' 
>>
>> make[3]: Entering directory 
>> `/home/rossier/xenomai-2.0/sim/gcic/gcc-build/i686-pc-linux-gnu/libio'
>> if [ x"no" = xyes ] && [ ! -d pic ]; then \
>>   mkdir pic; \
>> else true; fi
>> touch stamp-picdir
>> test x"no" != xyes ||\
>>   /home/rossier/xenomai-2.0/sim/gcic/gcc-build/gcc/xgcc 
>> -B/home/rossier/xenomai-2.0/sim/gcic/gcc-build/gcc/ 
>> -B/usr/realtime/libexec/gcic/i686-pc-linux-gnu/bin/ -c -g -O2 -I. 
>> -I../../../gcc-2.95.3/libio -D_IO_MTSAFE_IO  
>> ../../../gcc-2.95.3/libio/iogetline.c -o pic/iogetline.o 
>> /home/rossier/xenomai-2.0/sim/gcic/gcc-build/gcc/xgcc 
>> -B/home/rossier/xenomai-2.0/sim/gcic/gcc-build/gcc/ 
>> -B/usr/realtime/libexec/gcic/i686-pc-linux-gnu/bin/ -c -g -O2 -I. 
>> -I../../../gcc-2.95.3/libio -D_IO_MTSAFE_IO 
>> ../../../gcc-2.95.3/libio/iogetline.c
>> In file included from ../../../gcc-2.95.3/libio/libio.h:167,
>>                  from ../../../gcc-2.95.3/libio/iolibio.h:1,
>>                  from ../../../gcc-2.95.3/libio/libioP.h:47,
>>                  from ../../../gcc-2.95.3/libio/iogetline.c:26:
>> /usr/include/bits/stdio-lock.h:24: lowlevellock.h: No such file or 
>> directory
>> make[3]: *** [iogetline.o] Error 1
>> make[3]: Leaving directory 
>> `/home/rossier/xenomai-2.0/sim/gcic/gcc-build/i686-pc-linux-gnu/libio'
>> make[2]: *** [all-target-libio] Error 2
>> make[2]: Leaving directory `/home/rossier/xenomai-2.0/sim/gcic/gcc-build'
>> make[1]: *** [gcc-build/.gcic-built] Error 2
>> make[1]: Leaving directory `/home/rossier/xenomai-2.0/sim/gcic'
>> make: *** [all-recursive] Error 1
>> root@domain.hid#
>>
> 
> It seems to be an incompatibility issue between the NPTL and gcc-2.95.x:
> http://sources.redhat.com/ml/glibc-bugs/2004-06/msg00144.html
> 
> The best way to solve this would be to get rid of the MT support for 
> building the GCC-based instrumenter, since we don't need it, and libio/ 
> compilation would not break. I'll look at some way to fix this.
> 

Could you try the following steps and let me know if that works in your environment:

- unpack the gcc-2.95.3 archive
- apply the attached patch against the gcc tree
- pack back the tree
- configure, build and install Xenomai again to use the patched gcc archive for 
building the simulator.

In order to test the resulting stuff:

- export PATH=/usr/realtime/bin:$PATH
- export LD_LIBRARY_PATH=/usr/realtime/lib:$LD_LIBRARY_PATH
- cd xenomai-2.0/skins/vxworks/demos
- make sim

You should have the "satch_s" executable available in the current dir at that 
point; just start the following command then:
$ xenoscope satch_s

PS: at Xenomai configuration time, make sure to have selected the VxWorks skin 
among the APIs to build.

-- 

Philippe.

Re: [Xenomai-help] Usage of sim with xenomai-2.0

[Philippe Gerum]

ROSSIER Daniel wrote:
> Ok, I will also try to have a look. Maybe, an idea would be to migrate to gcc-3.4.4 for the code
> instrumentation...Are there specific issues related to the gcc version for that?
> 

There is big issue, unfortunately: the instrumenter is based on a patch against 
the C and C++ parsers that provides the needed support to insert code on-the-fly 
into the user code; it is this code which actually binds the application to the 
simulation engine. Crafting this patch is a rather complex business because you 
have to tap directly into GCC's lexer and grammar parser, and quite frankly, 
this is something I'm really reluctant to start anew on a radically different 
GCC parsing engine, at least now, with respect to the actual benefit upgrading 
the instrumenter base would bring. Again, usefulness / complexity ratio issue.

> Daniel
> 
> 
> -----Original Message-----
> From: Philippe Gerum [mailto:rpm@xenomai.org]
> Sent: Tue 10/25/2005 4:00 PM
> To: ROSSIER Daniel
> Cc: xenomai@xenomai.org
> Subject: Re: [Xenomai-help] Usage of sim with xenomai-2.0
>  
> ROSSIER Daniel wrote:
> 
>>Hi Philippe,
>>
>>Here is the info about my env:
>>
>>- kernel 2.6.9
>>- glibc 2.3.5
>>- gcc 3.4.4
>>- actually, I built my env. from scratch (no distro) - simply from www.linuxfromscratch.org
>>
>>But everything else works fine :-) (xenomai works perfectly. I tested it with the LinuxTraceToolkit, and it works as well)
>>
>>Here is the fragment of log, right before the failure (all the compilation steps before are OK):
>>
>>
>>make[4]: Leaving directory `/home/rossier/xenomai-2.0/sim/gcic/gcc-build/i686-pc-linux-gnu/libiberty'
>>make[3]: Leaving directory `/home/rossier/xenomai-2.0/sim/gcic/gcc-build/i686-pc-linux-gnu/libiberty'
>>make[3]: Entering directory `/home/rossier/xenomai-2.0/sim/gcic/gcc-build/i686-pc-linux-gnu/libio'
>>if [ x"no" = xyes ] && [ ! -d pic ]; then \
>>  mkdir pic; \
>>else true; fi
>>touch stamp-picdir
>>test x"no" != xyes ||\
>>  /home/rossier/xenomai-2.0/sim/gcic/gcc-build/gcc/xgcc -B/home/rossier/xenomai-2.0/sim/gcic/gcc-build/gcc/ -B/usr/realtime/libexec/gcic/i686-pc-linux-gnu/bin/ -c -g -O2 -I. -I../../../gcc-2.95.3/libio -D_IO_MTSAFE_IO  ../../../gcc-2.95.3/libio/iogetline.c -o pic/iogetline.o /home/rossier/xenomai-2.0/sim/gcic/gcc-build/gcc/xgcc -B/home/rossier/xenomai-2.0/sim/gcic/gcc-build/gcc/ -B/usr/realtime/libexec/gcic/i686-pc-linux-gnu/bin/ -c -g -O2 -I. -I../../../gcc-2.95.3/libio -D_IO_MTSAFE_IO ../../../gcc-2.95.3/libio/iogetline.c
>>In file included from ../../../gcc-2.95.3/libio/libio.h:167,
>>                 from ../../../gcc-2.95.3/libio/iolibio.h:1,
>>                 from ../../../gcc-2.95.3/libio/libioP.h:47,
>>                 from ../../../gcc-2.95.3/libio/iogetline.c:26:
>>/usr/include/bits/stdio-lock.h:24: lowlevellock.h: No such file or directory
>>make[3]: *** [iogetline.o] Error 1
>>make[3]: Leaving directory `/home/rossier/xenomai-2.0/sim/gcic/gcc-build/i686-pc-linux-gnu/libio'
>>make[2]: *** [all-target-libio] Error 2
>>make[2]: Leaving directory `/home/rossier/xenomai-2.0/sim/gcic/gcc-build'
>>make[1]: *** [gcc-build/.gcic-built] Error 2
>>make[1]: Leaving directory `/home/rossier/xenomai-2.0/sim/gcic'
>>make: *** [all-recursive] Error 1
>>root@domain.hid#
>>
> 
> 
> It seems to be an incompatibility issue between the NPTL and gcc-2.95.x:
> http://sources.redhat.com/ml/glibc-bugs/2004-06/msg00144.html
> 
> The best way to solve this would be to get rid of the MT support for building 
> the GCC-based instrumenter, since we don't need it, and libio/ compilation would 
> not break. I'll look at some way to fix this.
> 
> 
>>Thanks a lot.
>>
>>Cheers
>>
>>Daniel
>>
>>
>>
>>-----Message d'origine-----
>>De : Philippe Gerum [mailto:rpm@xenomai.org
>>Envoyé : mardi, 25. octobre 2005 15:03
>>À : ROSSIER Daniel
>>Cc : xenomai@xenomai.org
>>Objet : Re: [Xenomai-help] Usage of sim with xenomai-2.0
>>
>>ROSSIER Daniel wrote:
>>
>>
>>>Hi xeno-workers,
>>>
>>>
>>>
>>>I'm trying to compile the simulator of xenomai-2.0 within a kernel 2.6.9 
>>>but I get
>>>
>>>the following error when gcc-2.95.3 is being compiled: 
>>>"/usr/include/bits/stdio-lock.h:24: lowlevellock.h: No such file or 
>>>directory"
>>>
>>>(I presume that this include is not supported anymore by my current libc)
>>>
>>>
>>>
>>>I'm pretty sure that it is not a new issue - Sorry about this - I 
>>>probably missed the workaround.
>>>
>>
>>
>>This one is new actually. Could you send more information about your environment 
>>(glibc version, distro, compiler version) and the fragment of the output log 
>>containing the error message? TIA,
>>
>>
>>
>>>Please, would you be so kind as to help me?
>>>
>>>
>>>
>>>Thanks in advance
>>>
>>>
>>>
>>>Cheers
>>>
>>>Daniel
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>Dr. Daniel Rossier, Professeur
>>>
>>>REDS, Reconfigurable & Embedded Digital Systems, http://reds.eivd.ch/
>>>
>>>HES-SO
>>>
>>>Haute Ecole d'Ingénieurs et de Gestion (HEIG-VD)
>>>
>>>Rte de Cheseaux 1
>>>
>>>
>>>
>>>CH-1774 Yverdon-les-Bains
>>>
>>>
>>>
>>>Tél. fixe:     +41 24 557 62 69
>>>
>>>Tél. mobile:   +41 79 292 54 58
>>>
>>>E-mail:        daniel.rossier@domain.hid <mailto:daniel.rossier@domain.hidd.ch>
>>>
>>>
>>>
>>>
>>>------------------------------------------------------------------------
>>>
>>>_______________________________________________
>>>Xenomai-help mailing list
>>>Xenomai-help@domain.hid
>>>https://mail.gna.org/listinfo/xenomai-help
>>
>>
>>
> 
> 


-- 

Philippe.

Re: [Xenomai-help] Usage of sim with xenomai-2.0

[Philippe Gerum]

ROSSIER Daniel wrote:
> Well, I applied the patch and I was hopeful when it compiled the libio stuff. Unfortunately, the following error came out after a while:
> 
> /home/rossier/xenomai-2.0/sim/gcic/gcc-build/gcc/xgcc -B/home/rossier/xenomai-2.0/sim/gcic/gcc-build/gcc/ -B/usr/realtime/libexec/gcic/i686-pc-linux-gnu/bin/ -c -g -O2 -fvtable-thunks -D_GNU_SOURCE -fno-implicit-templates -I../../../gcc-2.95.3/libstdc++ -I../../../gcc-2.95.3/libstdc++/stl -I../libio -I../../../gcc-2.95.3/libstdc++/../libio -nostdinc++   ../../../gcc-2.95.3/libstdc++/stlinst.cc -o pic/stlinst.o
> /home/rossier/xenomai-2.0/sim/gcic/gcc-build/gcc/xgcc -B/home/rossier/xenomai-2.0/sim/gcic/gcc-build/gcc/ -B/usr/realtime/libexec/gcic/i686-pc-linux-gnu/bin/ -c -g -O2 -fvtable-thunks -D_GNU_SOURCE -fno-implicit-templates -I../../../gcc-2.95.3/libstdc++ -I../../../gcc-2.95.3/libstdc++/stl -I../libio -I../../../gcc-2.95.3/libstdc++/../libio -nostdinc++  ../../../gcc-2.95.3/libstdc++/stlinst.cc
> ../../../gcc-2.95.3/libstdc++/stl/stl_alloc.h: In instantiation of `__default_alloc_template<true,0>::_S_node_allocator_lock':
> ../../../gcc-2.95.3/libstdc++/stl/stl_alloc.h:394:   instantiated from `__default_alloc_template<true,0>::_Lock::~_Lock()'
> ../../../gcc-2.95.3/libstdc++/stl/stl_alloc.h:415:   instantiated from `__default_alloc_template<true,0>::allocate(unsigned int)'
> ../../../gcc-2.95.3/libstdc++/stlinst.cc:7:   instantiated from here
> ../../../gcc-2.95.3/libstdc++/stl/stl_alloc.h:581: Internal compiler error.
> ../../../gcc-2.95.3/libstdc++/stl/stl_alloc.h:581: Please submit a full bug report.
> ../../../gcc-2.95.3/libstdc++/stl/stl_alloc.h:581: See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions.
> make[2]: *** [stlinst.o] Error 1
> make[2]: Leaving directory `/home/rossier/xenomai-2.0/sim/gcic/gcc-build/i686-pc-linux-gnu/libstdc++'
> make[1]: *** [all-target-libstdc++] Error 2
> make[1]: Leaving directory `/home/rossier/xenomai-2.0/sim/gcic/gcc-build'
> make: *** [gcc-build/.gcic-built] Error 2
> root@domain.hid#  
> 
> 
> 'sounds bad :-(  No idea what it can be. Do you have an idea?
>

Nope. Unfortunately, whilst compiling the instrumenter is usually a no brainer 
on common distros, I have no clue wrt what your LFS setup is providing as libc 
headers, which seems to be at the root of the problem, since some of them are 
used to compile GCC against.

You could get rid of the C++ support if you don't plan to instrument C++ apps to 
run with the simulator, i.e.: in sim/gcic/GNUmakefile, just strip out "c++" from 
the LANG variable passed to the configure script, called from the 
gcc-build/.gcic-built rule. Just a work-around, but would perhaps allow you to 
build the simulator properly.

> 
> Daniel
> 
> 
> 
> -----Original Message-----
> From: Philippe Gerum [mailto:rpm@xenomai.org]
> Sent: Tue 10/25/2005 8:29 PM
> To: Philippe Gerum
> Cc: ROSSIER Daniel; xenomai@xenomai.org
> Subject: Re: [Xenomai-help] Usage of sim with xenomai-2.0
>  
> Philippe Gerum wrote:
> 
>>ROSSIER Daniel wrote:
>>
>>
>>>Hi Philippe,
>>>
>>>Here is the info about my env:
>>>
>>>- kernel 2.6.9
>>>- glibc 2.3.5
>>>- gcc 3.4.4
>>>- actually, I built my env. from scratch (no distro) - simply from 
>>>www.linuxfromscratch.org
>>>
>>>But everything else works fine :-) (xenomai works perfectly. I tested 
>>>it with the LinuxTraceToolkit, and it works as well)
>>>
>>>Here is the fragment of log, right before the failure (all the 
>>>compilation steps before are OK):
>>>
>>>
>>>make[4]: Leaving directory 
>>>`/home/rossier/xenomai-2.0/sim/gcic/gcc-build/i686-pc-linux-gnu/libiberty' 
>>>
>>>make[3]: Leaving directory 
>>>`/home/rossier/xenomai-2.0/sim/gcic/gcc-build/i686-pc-linux-gnu/libiberty' 
>>>
>>>make[3]: Entering directory 
>>>`/home/rossier/xenomai-2.0/sim/gcic/gcc-build/i686-pc-linux-gnu/libio'
>>>if [ x"no" = xyes ] && [ ! -d pic ]; then \
>>>  mkdir pic; \
>>>else true; fi
>>>touch stamp-picdir
>>>test x"no" != xyes ||\
>>>  /home/rossier/xenomai-2.0/sim/gcic/gcc-build/gcc/xgcc 
>>>-B/home/rossier/xenomai-2.0/sim/gcic/gcc-build/gcc/ 
>>>-B/usr/realtime/libexec/gcic/i686-pc-linux-gnu/bin/ -c -g -O2 -I. 
>>>-I../../../gcc-2.95.3/libio -D_IO_MTSAFE_IO  
>>>../../../gcc-2.95.3/libio/iogetline.c -o pic/iogetline.o 
>>>/home/rossier/xenomai-2.0/sim/gcic/gcc-build/gcc/xgcc 
>>>-B/home/rossier/xenomai-2.0/sim/gcic/gcc-build/gcc/ 
>>>-B/usr/realtime/libexec/gcic/i686-pc-linux-gnu/bin/ -c -g -O2 -I. 
>>>-I../../../gcc-2.95.3/libio -D_IO_MTSAFE_IO 
>>>../../../gcc-2.95.3/libio/iogetline.c
>>>In file included from ../../../gcc-2.95.3/libio/libio.h:167,
>>>                 from ../../../gcc-2.95.3/libio/iolibio.h:1,
>>>                 from ../../../gcc-2.95.3/libio/libioP.h:47,
>>>                 from ../../../gcc-2.95.3/libio/iogetline.c:26:
>>>/usr/include/bits/stdio-lock.h:24: lowlevellock.h: No such file or 
>>>directory
>>>make[3]: *** [iogetline.o] Error 1
>>>make[3]: Leaving directory 
>>>`/home/rossier/xenomai-2.0/sim/gcic/gcc-build/i686-pc-linux-gnu/libio'
>>>make[2]: *** [all-target-libio] Error 2
>>>make[2]: Leaving directory `/home/rossier/xenomai-2.0/sim/gcic/gcc-build'
>>>make[1]: *** [gcc-build/.gcic-built] Error 2
>>>make[1]: Leaving directory `/home/rossier/xenomai-2.0/sim/gcic'
>>>make: *** [all-recursive] Error 1
>>>root@domain.hid#
>>>
>>
>>It seems to be an incompatibility issue between the NPTL and gcc-2.95.x:
>>http://sources.redhat.com/ml/glibc-bugs/2004-06/msg00144.html
>>
>>The best way to solve this would be to get rid of the MT support for 
>>building the GCC-based instrumenter, since we don't need it, and libio/ 
>>compilation would not break. I'll look at some way to fix this.
>>
> 
> 
> Could you try the following steps and let me know if that works in your environment:
> 
> - unpack the gcc-2.95.3 archive
> - apply the attached patch against the gcc tree
> - pack back the tree
> - configure, build and install Xenomai again to use the patched gcc archive for 
> building the simulator.
> 
> In order to test the resulting stuff:
> 
> - export PATH=/usr/realtime/bin:$PATH
> - export LD_LIBRARY_PATH=/usr/realtime/lib:$LD_LIBRARY_PATH
> - cd xenomai-2.0/skins/vxworks/demos
> - make sim
> 
> You should have the "satch_s" executable available in the current dir at that 
> point; just start the following command then:
> $ xenoscope satch_s
> 
> PS: at Xenomai configuration time, make sure to have selected the VxWorks skin 
> among the APIs to build.
> 


-- 

Philippe.

RE: [Xenomai-help] Usage of sim with xenomai-2.0

[ROSSIER Daniel]

Hi Philippe,
Thanks a lot for your quick and efficient help.
I disabled c++ and it compiles.
But.. next challenge: trying to compile the whole sim, I get the following:

if ../../gcic/gcic -DHAVE_CONFIG_H -I. -I/home/rossier/tmp/xenomai-2.0/sim/skins/posix -I../../include  -D_GNU_SOURCE -D__IN_XENO__ --gcic-backend=/usr/realtime/libexec/gcic --skin-code  -I/home/rossier/tmp/xenomai-2.0/sim/skins/posix/.. -I/home/rossier/tmp/xenomai-2.0/sim/include -I/home/rossier/tmp/xenomai-2.0/source/skins -I/home/rossier/tmp/xenomai-2.0/source/include   -g -MT timer.o -MD -MP -MF ".deps/timer.Tpo" -c -o timer.o /home/rossier/tmp/xenomai-2.0/source/skins/posix/timer.c; \
then mv -f ".deps/timer.Tpo" ".deps/timer.Po"; else rm -f ".deps/timer.Tpo"; exit 1; fi
/home/rossier/tmp/xenomai-2.0/source/skins/posix/timer.c: In function `pse51_timer_create':
/home/rossier/tmp/xenomai-2.0/source/skins/posix/timer.c:153: warning: assignment makes pointer from integer without a cast
/home/rossier/tmp/xenomai-2.0/source/skins/posix/timer.c: In function `pse51_timer_delete':
/home/rossier/tmp/xenomai-2.0/source/skins/posix/timer.c:174: array subscript is not an integer
/home/rossier/tmp/xenomai-2.0/source/skins/posix/timer.c: In function `pse51_timer_settime':
/home/rossier/tmp/xenomai-2.0/source/skins/posix/timer.c:237: array subscript is not an integer
/home/rossier/tmp/xenomai-2.0/source/skins/posix/timer.c: In function `pse51_timer_gettime':
/home/rossier/tmp/xenomai-2.0/source/skins/posix/timer.c:294: array subscript is not an integer
/home/rossier/tmp/xenomai-2.0/source/skins/posix/timer.c: In function `pse51_timer_getoverrun':
/home/rossier/tmp/xenomai-2.0/source/skins/posix/timer.c:323: array subscript is not an integer
/home/rossier/tmp/xenomai-2.0/source/skins/posix/timer.c: In function `pse51_timer_cleanup_thread':
/home/rossier/tmp/xenomai-2.0/source/skins/posix/timer.c:353: warning: initialization makes pointer from integer without a cast
make[3]: *** [timer.o] Error 1
make[3]: Leaving directory `/home/rossier/tmp/xenomai-2.0/sim/skins/posix'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/home/rossier/tmp/xenomai-2.0/sim/skins/posix'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/rossier/tmp/xenomai-2.0/sim/skins'
make: *** [all-recursive] Error 1
rossier@domain.hid$   

Any idea about that?

Cheers
Daniel


-----Original Message-----
From: Philippe Gerum [mailto:rpm@xenomai.org]
Sent: Tue 10/25/2005 9:31 PM
To: ROSSIER Daniel
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] Usage of sim with xenomai-2.0
 
ROSSIER Daniel wrote:
> Well, I applied the patch and I was hopeful when it compiled the libio stuff. Unfortunately, the following error came out after a while:
> 
> /home/rossier/xenomai-2.0/sim/gcic/gcc-build/gcc/xgcc -B/home/rossier/xenomai-2.0/sim/gcic/gcc-build/gcc/ -B/usr/realtime/libexec/gcic/i686-pc-linux-gnu/bin/ -c -g -O2 -fvtable-thunks -D_GNU_SOURCE -fno-implicit-templates -I../../../gcc-2.95.3/libstdc++ -I../../../gcc-2.95.3/libstdc++/stl -I../libio -I../../../gcc-2.95.3/libstdc++/../libio -nostdinc++   ../../../gcc-2.95.3/libstdc++/stlinst.cc -o pic/stlinst.o
> /home/rossier/xenomai-2.0/sim/gcic/gcc-build/gcc/xgcc -B/home/rossier/xenomai-2.0/sim/gcic/gcc-build/gcc/ -B/usr/realtime/libexec/gcic/i686-pc-linux-gnu/bin/ -c -g -O2 -fvtable-thunks -D_GNU_SOURCE -fno-implicit-templates -I../../../gcc-2.95.3/libstdc++ -I../../../gcc-2.95.3/libstdc++/stl -I../libio -I../../../gcc-2.95.3/libstdc++/../libio -nostdinc++  ../../../gcc-2.95.3/libstdc++/stlinst.cc
> ../../../gcc-2.95.3/libstdc++/stl/stl_alloc.h: In instantiation of `__default_alloc_template<true,0>::_S_node_allocator_lock':
> ../../../gcc-2.95.3/libstdc++/stl/stl_alloc.h:394:   instantiated from `__default_alloc_template<true,0>::_Lock::~_Lock()'
> ../../../gcc-2.95.3/libstdc++/stl/stl_alloc.h:415:   instantiated from `__default_alloc_template<true,0>::allocate(unsigned int)'
> ../../../gcc-2.95.3/libstdc++/stlinst.cc:7:   instantiated from here
> ../../../gcc-2.95.3/libstdc++/stl/stl_alloc.h:581: Internal compiler error.
> ../../../gcc-2.95.3/libstdc++/stl/stl_alloc.h:581: Please submit a full bug report.
> ../../../gcc-2.95.3/libstdc++/stl/stl_alloc.h:581: See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions.
> make[2]: *** [stlinst.o] Error 1
> make[2]: Leaving directory `/home/rossier/xenomai-2.0/sim/gcic/gcc-build/i686-pc-linux-gnu/libstdc++'
> make[1]: *** [all-target-libstdc++] Error 2
> make[1]: Leaving directory `/home/rossier/xenomai-2.0/sim/gcic/gcc-build'
> make: *** [gcc-build/.gcic-built] Error 2
> root@domain.hid#  
> 
> 
> 'sounds bad :-(  No idea what it can be. Do you have an idea?
>

Nope. Unfortunately, whilst compiling the instrumenter is usually a no brainer 
on common distros, I have no clue wrt what your LFS setup is providing as libc 
headers, which seems to be at the root of the problem, since some of them are 
used to compile GCC against.

You could get rid of the C++ support if you don't plan to instrument C++ apps to 
run with the simulator, i.e.: in sim/gcic/GNUmakefile, just strip out "c++" from 
the LANG variable passed to the configure script, called from the 
gcc-build/.gcic-built rule. Just a work-around, but would perhaps allow you to 
build the simulator properly.

> 
> Daniel
> 
> 
> 
> -----Original Message-----
> From: Philippe Gerum [mailto:rpm@xenomai.org]
> Sent: Tue 10/25/2005 8:29 PM
> To: Philippe Gerum
> Cc: ROSSIER Daniel; xenomai@xenomai.org
> Subject: Re: [Xenomai-help] Usage of sim with xenomai-2.0
>  
> Philippe Gerum wrote:
> 
>>ROSSIER Daniel wrote:
>>
>>
>>>Hi Philippe,
>>>
>>>Here is the info about my env:
>>>
>>>- kernel 2.6.9
>>>- glibc 2.3.5
>>>- gcc 3.4.4
>>>- actually, I built my env. from scratch (no distro) - simply from 
>>>www.linuxfromscratch.org
>>>
>>>But everything else works fine :-) (xenomai works perfectly. I tested 
>>>it with the LinuxTraceToolkit, and it works as well)
>>>
>>>Here is the fragment of log, right before the failure (all the 
>>>compilation steps before are OK):
>>>
>>>
>>>make[4]: Leaving directory 
>>>`/home/rossier/xenomai-2.0/sim/gcic/gcc-build/i686-pc-linux-gnu/libiberty' 
>>>
>>>make[3]: Leaving directory 
>>>`/home/rossier/xenomai-2.0/sim/gcic/gcc-build/i686-pc-linux-gnu/libiberty' 
>>>
>>>make[3]: Entering directory 
>>>`/home/rossier/xenomai-2.0/sim/gcic/gcc-build/i686-pc-linux-gnu/libio'
>>>if [ x"no" = xyes ] && [ ! -d pic ]; then \
>>>  mkdir pic; \
>>>else true; fi
>>>touch stamp-picdir
>>>test x"no" != xyes ||\
>>>  /home/rossier/xenomai-2.0/sim/gcic/gcc-build/gcc/xgcc 
>>>-B/home/rossier/xenomai-2.0/sim/gcic/gcc-build/gcc/ 
>>>-B/usr/realtime/libexec/gcic/i686-pc-linux-gnu/bin/ -c -g -O2 -I. 
>>>-I../../../gcc-2.95.3/libio -D_IO_MTSAFE_IO  
>>>../../../gcc-2.95.3/libio/iogetline.c -o pic/iogetline.o 
>>>/home/rossier/xenomai-2.0/sim/gcic/gcc-build/gcc/xgcc 
>>>-B/home/rossier/xenomai-2.0/sim/gcic/gcc-build/gcc/ 
>>>-B/usr/realtime/libexec/gcic/i686-pc-linux-gnu/bin/ -c -g -O2 -I. 
>>>-I../../../gcc-2.95.3/libio -D_IO_MTSAFE_IO 
>>>../../../gcc-2.95.3/libio/iogetline.c
>>>In file included from ../../../gcc-2.95.3/libio/libio.h:167,
>>>                 from ../../../gcc-2.95.3/libio/iolibio.h:1,
>>>                 from ../../../gcc-2.95.3/libio/libioP.h:47,
>>>                 from ../../../gcc-2.95.3/libio/iogetline.c:26:
>>>/usr/include/bits/stdio-lock.h:24: lowlevellock.h: No such file or 
>>>directory
>>>make[3]: *** [iogetline.o] Error 1
>>>make[3]: Leaving directory 
>>>`/home/rossier/xenomai-2.0/sim/gcic/gcc-build/i686-pc-linux-gnu/libio'
>>>make[2]: *** [all-target-libio] Error 2
>>>make[2]: Leaving directory `/home/rossier/xenomai-2.0/sim/gcic/gcc-build'
>>>make[1]: *** [gcc-build/.gcic-built] Error 2
>>>make[1]: Leaving directory `/home/rossier/xenomai-2.0/sim/gcic'
>>>make: *** [all-recursive] Error 1
>>>root@domain.hid#
>>>
>>
>>It seems to be an incompatibility issue between the NPTL and gcc-2.95.x:
>>http://sources.redhat.com/ml/glibc-bugs/2004-06/msg00144.html
>>
>>The best way to solve this would be to get rid of the MT support for 
>>building the GCC-based instrumenter, since we don't need it, and libio/ 
>>compilation would not break. I'll look at some way to fix this.
>>
> 
> 
> Could you try the following steps and let me know if that works in your environment:
> 
> - unpack the gcc-2.95.3 archive
> - apply the attached patch against the gcc tree
> - pack back the tree
> - configure, build and install Xenomai again to use the patched gcc archive for 
> building the simulator.
> 
> In order to test the resulting stuff:
> 
> - export PATH=/usr/realtime/bin:$PATH
> - export LD_LIBRARY_PATH=/usr/realtime/lib:$LD_LIBRARY_PATH
> - cd xenomai-2.0/skins/vxworks/demos
> - make sim
> 
> You should have the "satch_s" executable available in the current dir at that 
> point; just start the following command then:
> $ xenoscope satch_s
> 
> PS: at Xenomai configuration time, make sure to have selected the VxWorks skin 
> among the APIs to build.
> 


-- 

Philippe.