rtems and coldfire: cannot build tools

[Erwin.Rol at transtechnik.com (Erwin Rol)]

I have had the same problem with on a dual pentium building
rtems i386 aout. The disk space isn't the problem for sure
cause i used a new UW 4.5 gig HD, that had only the rtems stuff on it.
It seems a problem from egcs it removes the include directory and
than tries to copy a file to it. I fixxed it by puttin a "mkdir include"
infront of the point where the copy happens.
I mentioned this before on the list but nobody seemed to have the
problem. 
I am at my work now so i can't check in wich file it was that i fixed
(well fixed isn't the right word i guess :-) but you should be able to 
find the point with grep or so :-)

- Erwin


joel at oarcorp.com wrote:
> 
> I have never seen a failure like this but, then again, have not seem many
> PowerMac Linux hosts either. :)
> 
> I suspect you ran out of disk space during the build.  It takes a lot of
> disk space to build and install the tools.
> 
> --joel
> Joel Sherrill                    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
> 
> On Tue, 9 Feb 1999, Benjamin Herrenschmidt wrote:
> 
> > Hi !
> >
> > I'm interested in rtms and I would like to try it with the Motorola
> > evaluation board (I have a sbc5206, and I downloaded a BSP for it from
> > <http://http://www.calm.hw.ac.uk/davidf/coldfire/rtems.htm>.
> >
> > I downloaded fresh tarballs of egcs-1.1b, binutils 2.9.1 and newlib
> > 1.8.0, applied the rtems patche successfully (no rejects), however when I
> > try "./bit m68k", after one or two hours of compile, I get the following
> > error:
> >
> >
> > Building fixed headers in /usr/src/rtems_tools/build-m68k-tools/gcc/include
> > Finding directories and links to directories
> >  Searching /usr/local/rtems/m68k-rtems/sys-include/.
> > All directories (including links to directories):
> >
> > Making symbolic directory links
> > Fixing directory /usr/local/rtems/m68k-rtems/sys-include into
> > /usr/src/rtems_tools/build-m68k-tools/
> > gcc/include
> > Checking header files
> > Fixing limits.h
> > Deleting /usr/src/rtems_tools/build-m68k-tools/gcc/include/limits.h; no
> > fixes were needed.
> > egrep: /usr/src/rtems_tools/build-m68k-tools/gcc/include/reg_types.h: No
> > such file or directory
> > egrep: /usr/src/rtems_tools/build-m68k-tools/gcc/include/regex.h: No such
> > file or directory
> > egrep: /usr/src/rtems_tools/build-m68k-tools/gcc/include/sys/lc_core.h:
> > No such file or directory
> > Cleaning up DONE files.
> > Removing unneeded directories:
> > rm -f include/syslimits.h
> > if [ -f include/limits.h ]; then \
> >   mv include/limits.h include/syslimits.h; \
> > else \
> >   cp ../../src/gcc/gsyslimits.h include/syslimits.h; \
> > fi
> > cp: cannot create regular file `include/syslimits.h': No such file or
> > directory
> > gmake[1]: *** [stmp-fixinc] Error 1
> > gmake[1]: Leaving directory `/usr/src/rtems_tools/build-m68k-tools/gcc'
> > gmake: *** [all-gcc] Error 2
> > ERROR: **** FAILED **** base build (step 1)
> >
> >
> > I'm building on a PowerMac running a recent 2.2.0 kernel, glibc-1.99 (the
> > "special" old PowerMac glibc) and egcs 1.1.1 (patched by Gary Thomas).
> > This config usually works fine for compiling things, and I did the
> > "install" test, it passsed (/tmp/foo/bar was correctly created).
> >
> > Any idea about what's going on ?
> >
> >
> > --
> >            E-Mail: <mailto:bh40 at calva.net>
> > BenH.      Web   : <http://calvaweb.calvacom.fr/bh40/>
> >
> >

-- 
  _/_/_/     _/_/_/           Erwin Rol
   _/         _/              mailto:Erwin.Rol at transtechnik.com
  _/ R A N S _/ E C H N I K   http://www.transtechnik.com/