Problems building gcc with Cygwin

Joel Sherrill joel.sherrill at OARcorp.com
Wed Jun 14 11:49:21 UTC 2000


Cygwin tool binaries are on the ftp site.  Why don't you
just use those?  

Besides -- egcs 1.1b and newlib 1.8.0 are very old.  Why
use them?

Palkin Andery wrote:
> 
> Hello!
> 
> I'm trying to install gcc-2.95.2 on winNT (CygWin 20.0).
> I'm doing next steps:
>    - apply the patch gcc-2.95.2-rtems-20000427.diff.gz
>    - Remove directories: - source\egcs-1.1b\libf2c
>                          - source\egcs-1.1b\gcc\objc
>                          - source\egcs-1.1b\gcc\f
>    - link directories: -  ln -s ../newlib-1.8.0/newlib newlib
>                        -  ln -s ../newlib-1.8.0/libgloss libgloss
>    - configure:
>                cd /build/egcs
>                /source/gcc-2.95.2/configure --verbose \
>                                             --target=m68k-rtems \
>                                             --prefix=/gcc-m68k-rtems \
>                                             --with-local-prefix=/gcc-m68k-rtems \
>                                             --with-gnu-as \
>                                             --with-gnu-ld \
>                                             --with-newlib
>    - install  autoconf package
>    - compile by command "make cross" and at this step i am getting error:
>   ------------------
> for name in _muldi3 _divdi3 _moddi3 _udivdi3 _umoddi3 _negdi2 _lshrdi3 _ashldi3 _ashrdi3
>   _ffsdi2 _udiv_w_sdiv _udivmoddi4 _cmpdi2 _ucmpdi2 _floatdidf _floatdisf _fixunsdfsi
>   _fixunssfsi _fixunsdfdi _fixdfdi _fixunssfdi _fixsfdi _fixxfdi _fixunsxfdi _floatdixf
>   _fixunsxfsi _fixtfdi _fixunstfdi _floatditf __gcc_bcmp _varargs __dummy _eprintf _bb
>   _shtab _clear_cache _trampoline __main _exit _ctors _pure; \
> do \
>   echo ${name}; \
>   /build/egcs/gcc/xgcc -B/build/egcs/gcc/ -B/gcc-m68k-rtems/m68k-rtems/bin/
>     -I/gcc-m68k-rtems/m68k-rtems/include -O2 -I/source/gcc-2.95.2/gcc/../newlib/libc/sys
>      /rtems/include -DCROSS_COMPILE -DIN_GCC     -g -O2 -I./include -g1  -DIN_LIBGCC2
>     -D__GCC_FLOAT_NOT_NEEDED -Dinhibit_libc   -I. -I/source/gcc-2.95.2/gcc -I/source
>     /gcc-2.95.2/gcc/config -I/source/gcc-2.95.2/gcc/../include -c -DL${name} \
>        /source/gcc-2.95.2/gcc/libgcc2.c -o ${name}.o; \
>   if [ $? -eq 0 ] ; then true; else exit 1; fi; \
>   m68k-rtems-ar rc tmplibgcc2.a ${name}.o; \
>   rm -f ${name}.o; \
> done
> _muldi3
> /tmp/ccYSVVk2.s: Assembler messages:
> /tmp/ccYSVVk2.s:86: Warning: .type pseudo-op used outside of .def/.endef ignored
> .
> /tmp/ccYSVVk2.s:86: Error: Rest of line ignored. First ignored character is `_'.
> 
> /tmp/ccYSVVk2.s:112: Warning: .size pseudo-op used outside of .def/.endef ignore
> d.
> /tmp/ccYSVVk2.s:112: Error: Rest of line ignored. First ignored character is `_'
> .
> make[3]: *** [libgcc2.a] Error 1
> make[3]: Leaving directory `/build/egcs/gcc'
> make[2]: *** [stmp-multilib-sub] Error 2
> make[2]: Leaving directory `/build/egcs/gcc'
> make[1]: *** [stmp-multilib] Error 1
> make[1]: Leaving directory `/build/egcs/gcc'
> make: *** [cross] Error 2
>   ------------------
> 
> Have You got any ideas?
> Thanks.

-- 
Joel Sherrill, Ph.D.             Director of Research & Development
joel at OARcorp.com                 On-Line Applications Research
Ask me about RTEMS: a free RTOS  Huntsville AL 35805
   Support Available             (256) 722-9985



More information about the users mailing list