rtems and coldfire: cannot build tools

[benh at mipsys.com (Benjamin Herrenschmidt)]

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/>