Problems building egcs-1.1b with Cigwin

[Gus Paolone]

Hi Denis;

I finally go things going. What I found is that the instructions in the
Getting Started guide for CygWin shows two different --prefix when
building binutil and egcs. Once I made these the same the build was able
to pickup the correct assembler to build libgcc1.

I also had problems building RTEMS. What I found was that the build was
picking up the incorrect limits.h file. This is something to do with the
CygWin installation. Apparently the bit script for non-CygWin builds
does this correctly.

What I ended up doing was to put the full path of the correct limits.h
on the file it was asking for (I cannot remember the file name) and it
was able to compile. However I need to fix this by copying the correct
limits.h to the correct directory (which I have not yet worked out).
Apparently the latest egcs and  RTEMS patches correct this problem.

Well, for now I have to get busy modifying gen68360 to work on my board.

Gus.

Denis Rouleau wrote:
> 
> Hi there.
> 
> I tried to get things going with RTEMS for the 68360 on an NT laptop and
> after many days of frustration, I simply gave up. My schedule didn't allow
> me to waste any more time on it.
> 
> I would be very interested in your outcome. Please let me know how things go
> for you.
> 
> Best of luck.
> 
> Denis Rouleau
> 
> ----- Message d'origine -----
> De : Gus Paolone <gus.paolone at fujitsu.com.au>
> À : <rtems-users at oarcorp.com>
> Envoyé : Wednesday, January 05, 2000 4:26 PM
> Objet : Problems building egcs-1.1b with Cigwin
> 
> > Hi
> >
> > I would really appreciate some help building egcs-1.1b. I have already
> > built and installed the binutil with no problems after following Chapter
> > 7.4 of the "Getting Started with RTEMS for C/C++ Users". However when I
> > follow the steps detailed in Chapter 7.5 I get stuck when I do the "make
> > cross".
> >
> > My shell is Cigwin B20.1 running on Win98. I took some of the advice
> > that's available and updated Make to Make 3.77 but this had no effect.
> >
> > I'm building for 68K (68360 actually) and it seems it doesn't like
> > building libgcc1.s. I read somewhere that you cannot build this library
> > using the cross GCC just built, but from what I see this is exactly what
> > its doing when it fails.
> >
> > I've also just read in the CrossGCC FAQs that the --prefix when building
> > the binutils and egcs should be the same. However the Getting Started
> > guide uses a different path. Is this a problem?
> >
> > See below my transcript of events (Note that I've cut out many lines of
> > compilation):
> >
> > ude/va-clipper.h ./ginclude/va-spur.h ./ginclude/va-m32r.h
> > ./ginclude/va-sh.h ./
> > ginclude/va-v850.h ./ginclude/va-arc.h ./ginclude/iso646.h
> > ./ginclude/va-ppc.h .
> > /ginclude/math-68881.h ./cp/inc/typeinfo ./cp/inc/exception
> > ./cp/inc/new ./cp/in
> > c/new.h ./ginclude/proto.h ./ginclude/stdbool.h; do \
> >   if [ X$file != X.. ]; then \
> >     realfile=`echo $file | sed -e 's|.*/\([^/]*\)$|\1|'`; \
> >     touch include/$realfile; \
> >     rm -f include/$realfile; \
> >     cp $file include; \
> >     chmod a+r include/$realfile; \
> >   fi; \
> > done
> > rm -f include/limits.h
> > cp xlimits.h include/limits.h
> > chmod a+r include/limits.h
> > rm -f include/float.h
> > if [ -s gfloat.h ]; then \
> >   cp gfloat.h include/float.h && \
> >   chmod a+r include/float.h; \
> > else :; fi
> > rm -f include/README
> > cp ./README-fixinc include/README
> > chmod a+r include/README
> > touch stmp-int-hdrs
> > if [ -f libgcc2.ready ] ; then \
> >         true; \
> > else \
> >         touch libgcc2.ready; \
> > fi
> > rm -f tmplibgcc1.a libgcc1.S
> > cp ./config/m68k/lb1sf68.asm libgcc1.S
> > for name in _mulsi3 _udivsi3 _divsi3 _umodsi3 _modsi3 _double
> > _float _floatex _e
> > qdf2 _nedf2 _gtdf2 _gedf2 _ltdf2 _ledf2 _eqsf2 _nesf2 _gtsf2 _gesf2
> > _ltsf2 _lesf
> > 2; \
> > do \
> >   echo ${name}; \
> >   /gus/rtems/tools/egcs-1.1b/gcc/xgcc
> > -B/gus/rtems/tools/egcs-1.1b/gcc/ -O2  -DC
> > ROSS_COMPILE -DIN_GCC    -g -I./include   -g1  -DIN_LIBGCC2
> > -D__GCC_FLOAT_NOT_NE
> > EDED -Dinhibit_libc  -I. -I. -I./config -c -DL${name} libgcc1.S; \
> >   if [ $? -eq 0 ] ; then true; else exit 1; fi; \
> >   mv libgcc1.o ${name}.o; \
> >   m68k-rtems-ar rc tmplibgcc1.a ${name}.o; \
> >   rm -f ${name}.o; \
> > done
> > _mulsi3
> > as: unrecognized option `-c68020'
> > make[1]: *** [libgcc1-asm.a] Error 1
> > make[1]: Leaving directory `/gus/rtems/tools/egcs-1.1b/gcc'
> > make: *** [cross] Error 2
> > ~/rtems/tools/egcs-1.1b [13]
> >
> >
> > Thanks for the help in advance :-)
> >
> > Regards
> >
> > Gus Paolone.
> >