Ralf Corsepius corsepiu at faw.uni-ulm.de
Wed Jun 26 14:38:37 UTC 2002

Am Die, 2002-06-25 um 15.48 schrieb Philip Nye:
> Hello,
> As an RTEMS newbie, can anyone summarise for me what is different about the
> RTEMS gcc toolset from other gcc releases - I am interested in the Coldfire
> version.
Check out the patches to gcc and newlib provided somewhere on
ftp://ftp.oarcorp.com and you will see the differences.

They vary from version to version. Sometimes they contain patches to a
particular target's setup, sometimes they contain bug fixes, sometimes
adaptions to particular versions of newlib/RTEMS, sometimes ...

> Is there any reason why I can't use m68k-elf-gcc version 2.97 or later for
> compiling RTEMS?
Yes, 2 main reasons:

1. There is no such thing as a generic m68k-elf-gcc, because each gcc
binary in general is tightly coupled to a particular OS and its libc. 

So you might have some success in using your m68k-elf-gcc for RTEMS if
it is compiled against a sufficiently compatible version of newlib to
the one rtems-gcc uses -  However, YMMV significantly.

2. RTEMS internally uses a restrictive naming for the target (cross-)
tools. They are required to be named <target>-rtems-<tool>

You would have to (link/copy) your m68k-elf-<tools> to m68k-rtems-gcc to
be able to use them.

I.e. there are ways to use such a gcc for RTEMS, but I would not
recommend using such a m68k-elf-gcc for RTEMS - Grabbing the binaries or
sources of from ftp.oarcorp.com is by far much easier than to struggle
with another toolchain.


More information about the users mailing list