Errors building GCC for m68k in Beta3a

Tue Oct 31 12:41:11 UTC 2000

I'm no Cygwin expert, but is there a problem with DOS text format files
here?  I know the pre-processor can't manage multi-line macros if lines are
terminated with CR/LF.

-- Nick Simon 

> -----Original Message-----
> From: DeanNelson at aol.com [mailto:DeanNelson at aol.com]
> Sent: 31 October 2000 12:32
> To: rtems-users at oarcorp.com
> Subject: Errors building GCC for m68k in Beta3a
> 
> 
> Hello,
> I'm using CYGWIN and following the directions in the "Getting 
> Started with 
> RTEMS for C/C++ Users" manual. I have all of the components 
> listed and when I 
> run the "bit" script to build the tools binutils builds 
> correctly, but gcc 
> errors out in the "elfos.h" file. I have looked at it and it 
> looks all right. 
> I have POSIX, ITron, and MP turned off. I have tried these 
> but to no avail:
> ./bit m68k
> ./bit m68k-coff
> ./bit m68k-elf
> 
> What am I doing wrong? Any help you can offer would be appreciated! 
> Thanks,
> Dean Nelson
> 
> --------------------------------ERRORS 
> FOLLOW---------------------------------------------------------
> 
> Building a cross GNU C/C++ toolset with the following configuration:
>     BINUTILS      -->  binutils-2.9.5.0.24
>     GCC           -->  gcc-2.95.2
>     NEWLIB        -->  newlib-1.8.2
>     TARGET        -->  m68k-rtems
>     INSTALL POINT -->  /opt/rtems
>     BUILD DOCS    -->  no
> 
> ....
> ....
> ....
> make[2]: Leaving directory `/gcctools/tools/build-m68k-tools/texinfo'
> make[1]: Leaving directory `/gcctools/tools/build-m68k-tools/texinfo'
> make[1]: Entering directory `/gcctools/tools/build-m68k-tools/etc'
> make[1]: Nothing to be done for `all'.
> make[1]: Leaving directory `/gcctools/tools/build-m68k-tools/etc'
> make[1]: Entering directory `/gcctools/tools/build-m68k-tools/gcc'
> gcc -DCROSS_COMPILE -DIN_GCC     -O2 -g  -DHAVE_CONFIG_H    -I. 
> -I../../gcc-2.95.2/gcc -I../../gcc-2.95.2/gcc/config 
> -I../../gcc-2.95.2/gcc/../include \
>   
> -DGCC_INCLUDE_DIR=\"/opt/rtems/lib/gcc-lib/m68k-rtems/2.95.2/i
> nclude\" \
>   
> -DGPLUSPLUS_INCLUDE_DIR=\"/opt/rtems/lib/gcc-lib/m68k-rtems/2.
> 95.2/../../../..
> 
> `echo /opt/rtems | sed -e 's|^/opt/rtems||' -e 
> 's|/[^/]*|/..|g'`/include/g++-3\" \
>   -DLOCAL_INCLUDE_DIR=\"/opt/rtems/include\" \
>   
> -DCROSS_INCLUDE_DIR=\"/opt/rtems/lib/gcc-lib/m68k-rtems/2.95.2
> /../../../../m68
> 
> k-rtems/sys-include\" \
>   
> -DTOOL_INCLUDE_DIR=\"/opt/rtems/lib/gcc-lib/m68k-rtems/2.95.2/
> ../../../../m68k
> 
> -rtems/include\" \
>   -c `echo ../../gcc-2.95.2/gcc/cccp.c | sed 's,^\./,,'`
> In file included from 
> ../../gcc-2.95.2/gcc/config/m68k/m68020-elf.h:26,
>                  from ../../gcc-2.95.2/gcc/config/m68k/rtemself.h:25,
>                  from tm.h:5,
>                  from ../../gcc-2.95.2/gcc/config/i386/xm-i386.h:43,
>                  from config.h:8,
>                  from ../../gcc-2.95.2/gcc/cccp.c:21:
> ../../gcc-2.95.2/gcc/config/elfos.h:43: parse error before `do'
> ../../gcc-2.95.2/gcc/config/elfos.h:43: stray '\' in program
> ../../gcc-2.95.2/gcc/config/elfos.h:44: stray '\' in program
> ../../gcc-2.95.2/gcc/config/elfos.h:45: stray '\' in program
> ../../gcc-2.95.2/gcc/config/elfos.h:46: stray '\' in program
> In file included from 
> ../../gcc-2.95.2/gcc/config/m68k/m68020-elf.h:26,
>                  from ../../gcc-2.95.2/gcc/config/m68k/rtemself.h:25,
>                  from tm.h:5,
>                  from ../../gcc-2.95.2/gcc/config/i386/xm-i386.h:43,
>                  from config.h:8,
>                  from ../../gcc-2.95.2/gcc/cccp.c:21:
> ../../gcc-2.95.2/gcc/config/elfos.h:108: parse error before `('
> ../../gcc-2.95.2/gcc/config/elfos.h:108: parse error before `)'
> ../../gcc-2.95.2/gcc/config/elfos.h:136: stray '\' in program
> ../../gcc-2.95.2/gcc/config/elfos.h:137: stray '\' in program
> ../../gcc-2.95.2/gcc/config/elfos.h:150: stray '\' in program
> .....
> .....
> ../../gcc-2.95.2/gcc/cccp.c:9548: parse error before 
> `__builtin_next_arg'
> ../../gcc-2.95.2/gcc/cccp.c: In function `pedwarn_with_file_and_line':
> ../../gcc-2.95.2/gcc/cccp.c:9575: `va_list' undeclared (first 
> use in this 
> function)
> ../../gcc-2.95.2/gcc/cccp.c:9575: parse error before `args'
> ../../gcc-2.95.2/gcc/cccp.c:9580: `args' undeclared (first 
> use in this 
> function)
> ../../gcc-2.95.2/gcc/cccp.c:9580: `__gnuc_va_list' undeclared 
> (first use in 
> this function)
> ../../gcc-2.95.2/gcc/cccp.c:9580: parse error before 
> `__builtin_next_arg'
> ../../gcc-2.95.2/gcc/cccp.c: In function `fatal':
> ../../gcc-2.95.2/gcc/cccp.c:10614: `va_list' undeclared 
> (first use in this 
> function)
> ../../gcc-2.95.2/gcc/cccp.c:10614: parse error before `args'
> ../../gcc-2.95.2/gcc/cccp.c:10617: `args' undeclared (first 
> use in this 
> function)
> ../../gcc-2.95.2/gcc/cccp.c:10617: `__gnuc_va_list' 
> undeclared (first use in 
> this function)
> ../../gcc-2.95.2/gcc/cccp.c:10617: parse error before 
> `__builtin_next_arg'
> make[1]: *** [cccp.o] Error 1
> make[1]: Leaving directory `/gcctools/tools/build-m68k-tools/gcc'
> make: *** [all-gcc] Error 2
> ERROR: **** FAILED **** base build (step 1)
> 
> Started:   Mon Oct 30 23:26:46 2000
> Finished:  Mon Oct 30 23:44:25 2000
> 
> Directory size information:
> 2285    build-m68k-tools
> 95606   /opt/rtems
> 
> The src and build-m68k-tools subdirectory have NOT been removed.
> 

**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.

This footnote also confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses.

www.mimesweeper.com
**********************************************************************