[ANNOUNCE] GCC 3.3.1 uClinux/ColdFire toolchain (20030725 snapshot)

[Bernardo Innocenti]

On Monday 28 July 2003 08:09, Dan Kegel wrote:

> > I've already built a m68k-elf toolchain ...
>
> I've noticed that, when you start trying to use the testsuites, you have
> to pay closer attention to the build/host/target names you use.

arm-elf was an easy pick for me since there it has a simulator in gdb
and it's being used as the example in the combined tree tutorial ;-)

> It looks like the name arm-uclinux is in use, and makes more sense than
> arm-elf, at least to me;
> [...]
> I'd expect m68k-uclinux to also be popular?

With the latest official uClinux toolchain (2.95.3 based), they were
still using m68k-elf with several unclean tweaks in the header files.

I've built on top of that mess, but before I submit any patches
touching the target configuration, I'll have to create the
m68k-uclinux-elf myself.

I've not yet figured out how to do it all over the toolchain, but
looking at config.gcc it appears to be quite straightforward.


> I wouldn't be suprised if you had to call your target
> m68k-unknown-uclinux-gnu to make e.g. binutils' or gcc's test suite happy. 
> Dejagnu tends to get upset if you don't have several dashes in the target
> :-)

Argh, then I'll have to struggle on this too ;-)


> Be sure to use a recent version of inetutils.  Older ones
> didn't set the environment properly in rshd.  BTW you need all three,
> probably: rshd, rlogind, and rcp.

Yes, I've read it in your docs. Thank you very much for saving me
a week worth of guessing.


> Hopefully this'll shake out a few bugs in gcc-3.3.1 before release...
> or more likely, in 3.4, if you test that...

I'm testing with gcc-3.3.1 branch because my patch apply on it as-is.

I'll start porting those to HEAD when I've shaken out the remaining
bugs on the stable branch.

-- 
  // Bernardo Innocenti - Develer S.r.l., R&D dept.
\X/  http://www.develer.com/

Please don't send Word attachments - http://www.gnu.org/philosophy/no-word-attachments.html