Problem to save file on the hard disk! What I have to set to do it ?

Joel Sherrill joel.sherrill at oarcorp.com
Mon Mar 20 13:50:37 UTC 2006


Matteo wrote:

>Hi Joel,
>following your suggestion I follow the 
>http://www.rtems.com/wiki/index.php/RTEMSAda guide, but I have a problem.
>I download from the cvs rtems and I have only this in the directory;
>
>acinclude.m4 aclocal automake bootstrap bpskit c 
>
>So, like the guide suggests, I launch ./bootstrap but I have this error  ;
>
>bash: ./bootstrap. /bin/sh^M: bad interpreter: no such file or directory
>
>  
>
This looks like something happened with CR/LF on the CVS checkout.   My 
guess would
be that you are on Cygwin and somehow using a partition with automatic 
CR/LF.

>So I try the launch the other executable file ./acinclude.m4 and I have this 
>error;
>
>root at matteo:/usr/local/rtems/source/tools/rtems-4.7# ./acinclude.m4
>: command not founde 5:
>./acinclude.m4: line 6: syntax error near unexpected token 
>`2.59' '/acinclude.m4: line 6: `AC_PREREQ(2.59)
>
>What means ?
>
>I have installed autoconf-2.59 and automake-1.9.6, with newlib-1.13.0, binutils-
>2.16.1, gcc-4.0.2
>
>Somebody can help me ?
>
>Thanks in advance
>
>Matteo
>
>Scrive Joel Sherrill <joel.sherrill at oarcorp.com>:
>
>  
>
>>Matteo wrote:
>>
>>    
>>
>>>Hi Joel,
>>>I'm reistalling RTEMS with the following ;
>>>binutils-2.16.1
>>>newlib-1.13.0
>>>gcc-4.0.2
>>>rtems from the cvs
>>>but I have the problem compiling gcc-4.0.2, like this ;
>>>..
>>>..
>>>-DL_fixunsdfsi -c ../../gcc-4.0.2/gcc/libgcc2.c -o libgcc/./_fixunsdfsi.o
>>>In file included from
>>>      
>>>
>>/usr/local/rtems/source/tools/b-gcc/gcc/include/syslimits.h:7,
>>    
>>
>>>                from
>>>      
>>>
>>/usr/local/rtems/source/tools/b-gcc/gcc/include/limits.h:11,
>>    
>>
>>>                from ../../gcc-4.0.2/gcc/libgcc2.c:1487:
>>>/usr/local/rtems/source/tools/b-gcc/gcc/include/limits.h:122:61: error: no
>>>include path in which to search for limits.h
>>>make[2]: *** [libgcc/./_fixunsdfsi.o] Error 1
>>>make[2]: Leaving directory `/usr/local/rtems/source/tools/b-gcc/gcc'
>>>make[1]: *** [stmp-multilib] Error 2
>>>make[1]: Leaving directory `/usr/local/rtems/source/tools/b-gcc/gcc'
>>>make: *** [all-gcc] Error 2
>>>make: Leaving directory `/usr/local/rtems/source/tools/b-gcc'
>>>root at matteo:/usr/local/rtems/source/tools/b-gcc#
>>>
>>>So I don't know why ?
>>>I have add the following path before start all the installation ;
>>>export PATH="$PATH:/usr/local/rtems/rtems4.7/bin"
>>>
>>>But it said me that can't find the limit.h, but I don't know wich other path
>>>      
>>>
>>I
>>    
>>
>>>have to add!
>>>Can you help me ?
>>>
>>> 
>>>
>>>      
>>>
>>http://www.rtems.com/wiki/index.php/RTEMSAda is Laurent Guerby's notes 
>>on building
>>a C/Ada toolset. When you see --enable-languages your options are c, 
>>c++, and ada.
>>Those are pretty easy to follow.
>>
>>    
>>
>>>Scrive Joel Sherrill <joel.sherrill at oarcorp.com>:
>>>
>>> 
>>>
>>>      
>>>
>>>>Matteo wrote:
>>>>
>>>>   
>>>>
>>>>        
>>>>
>>>>>Infact I installed this version of rtems because with that suggested from
>>>>>     
>>>>>
>>>>>          
>>>>>
>>>>the
>>>>   
>>>>
>>>>        
>>>>
>>>>>"download helper" I had some problem.
>>>>>So, I decid to reinstall all rtems with the version suggest from the
>>>>>     
>>>>>
>>>>>          
>>>>>
>>>>download
>>>>   
>>>>
>>>>        
>>>>
>>>>>helper(so I'm sure that all the samples works!);
>>>>>gcc-3.2.3
>>>>>newlib-1.11.0
>>>>>binutils-2.13.2.1
>>>>>rtems-4.6.5
>>>>>So I applied the patch for gcc and newlib, a export the 
>>>>>export PATH="$PATH:/usr/local/rtems/rtems4.7/bin" 
>>>>>
>>>>>I configure binutils in this way;
>>>>>
>>>>>../binutils-2.16.1/configure --target=i386-rtems4.7 
>>>>>--prefix=/usr/local/rtems/rtems4.7
>>>>>
>>>>>
>>>>>
>>>>>     
>>>>>
>>>>>          
>>>>>
>>>>You downloaded a 4.6 release and toolset and are configuring it for
>>>>rtems 4.7.  RTEMS tools have evolved so you can have toolsets for
>>>>multiple verions of RTEMS installed concurrently.  They follow
>>>>this history:
>>>>
>>>>Version         Prefix           Naming
>>>>======  ==========  =================
>>>> 4.5         /opt/rtems        CPU-rtems-TOOL
>>>> 4.6        /opt/rtems-4.6   CPU-rtems-TOOL
>>>> 4.7        /opt/rtems-4.7   CPU-rtems4.7-TOOL
>>>>
>>>>For each RTEMS release series, there is a matched C library version
>>>>an recommended GCC version.  Sometimes depending on the compiler,
>>>>you can change the GCC version a little but the C library version is
>>>>mated and should be used.
>>>>
>>>>You are mismatching things.
>>>>
>>>>   
>>>>
>>>>        
>>>>
>>>>>and I launch "make -w all install", but I have this error ;
>>>>>..
>>>>>..
>>>>>Wmissing-prototypes -g -O2 -c ../../binutils-2.13.2.1/gas/app.c
>>>>>In file included from ./targ-cpu.h:1,
>>>>>               from ../../binutils-2.13.2.1/gas/config/obj-elf.h:42,
>>>>>               from ./obj-format.h:1,
>>>>>               from ../../binutils-2.13.2.1/gas/config/te-generic.h:19,
>>>>>               from ./targ-env.h:1,
>>>>>               from ../../binutils-2.13.2.1/gas/as.h:614,
>>>>>               from ../../binutils-2.13.2.1/gas/app.c:30:
>>>>>../../binutils-2.13.2.1/gas/config/tc-i386.h:530: error: array type has
>>>>>incomplete element type
>>>>>make[3]: *** [app.o] Error 1
>>>>>make[3]: Leaving directory `/usr/local/rtems/source/tools/b-binutils/gas'
>>>>>make[2]: *** [all-recursive] Error 1
>>>>>make[2]: Leaving directory `/usr/local/rtems/source/tools/b-binutils/gas'
>>>>>make[1]: *** [all-recursive-am] Error 2
>>>>>make[1]: Leaving directory `/usr/local/rtems/source/tools/b-binutils/gas'
>>>>>make: *** [all-gas] Error 2
>>>>>make: Leaving directory `/usr/local/rtems/source/tools/b-binutils'
>>>>>root at matteo:/usr/local/rtems/source/tools/b-binutils#
>>>>>
>>>>>
>>>>>That was the same error that convinced me to try another version of
>>>>>          
>>>>>
>>rtems.
>>    
>>
>>>>>So have you some idea about to resolve this configuration problem ?
>>>>>
>>>>>Thanks in advance 
>>>>>
>>>>>MAtteo
>>>>>
>>>>>
>>>>>
>>>>>     
>>>>>
>>>>>          
>>>>>
>>>>   
>>>>
>>>>        
>>>>
>>>
>>>
>>> 
>>>
>>>      
>>>
>>
>>    
>>
>
>
>
>
>  
>




More information about the users mailing list