RTEMS vs. egcs-1.1a

[joel at oarcorp.com (joel at oarcorp.com)]

On Mon, 7 Sep 1998, Ralf Corsepius wrote:

> 1) Build a unified source tree (one-tree) of all tools
> cp -a /lfs/hermes/embedded/newlib-1.8.0-rtems-19980707/* ${SRCDIR}
> cp -a /usr/src/packages/egcs/egcs-1.1b/* ${SRCDIR}
> cp -a /usr/src/packages/gas/gas-980902/* ${SRCDIR}

This should also be possible with careful application of symlinks. 

> Furthermore, I noticed:
> * The toplevel configure scripts (cygnus configure scripts) in gas and egcs are
> inconsistent, i.e. egcs' configure script doesn't work with gas-snapshots
> (binutils-2.9.2 snapshots). egcs' toplevel configure script doesn't support
> libintl, and gas' configure script does not support "make cross". However I assume
> egcs' configure script to work with binutils-2.9.1.

I have reported this to both egcs and the binutils snapshot list.

> * Using a symlinked one-tree presumably works for egcs+binutils, but doesn't seem
> to work with gas-snapshots.

It would appear so since I build all the tool targets with binutils 2.9.1
and a pre-1.1 egcs snapshot.

> * Once a c/c++ toolchain has been installed, "make all and/or make
> install" seems to be sufficient for a full build over all languages
> (objc seems to access include files from the installed tool-chain when
> building egcs) for many targets, but fails for some. 

Objective C has always had some problems building cross.

Were the problems related to binutils?

> * I successfully applied the procedure above for --target=sh-rtems and
> --target=m68k-rtems on a linux host, alternatively using ether gcc-2.7.2.3 or
> egcs-1.1b in conjunction with binutils-2.9.1.0.11.

Great.  I use gcc 2.8.1 as the foundation for gnat/rtems toolsets and have
not had any problems with sparc, powerpc, or i386.  But that was with
binutils 2.9.1.

--joel