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

[Dan Kegel]

Bernardo Innocenti wrote:
> On Saturday 26 July 2003 05:28, Dan Kegel wrote:
> 
>>[Have you considered running the gcc regression tests on your new cross-compiler?]
>>http://www.kegel.com/crosstool/crosstool-0.14/doc/chroot-login-howto.html
>>covers setting up rsh and rcp into a chroot jail (convenient for testing
>>new shared C libraries without upsetting the system).
>>http://www.kegel.com/crosstool/crosstool-0.14/doc/dejagnu-remote-howto.html
>>covers bringing up dejagnu for remote testing.
>>http://www.kegel.com/crosstool/crosstool-0.14/doc/crosstool-howto.html
>>covers how to bring up and test a cross toolchain based on gcc and glibc
>>(ok, not directly applicably, but I thought I'd mention it).
> 
> 
> Thank you! I've just managed to run the testsuite for arm-elf with simulator
> with the GCC 3.3.1 branch. Guessing the correct CVS tags to use for all the
> other modules was the hardest part :-/

I've found http://www.gregorpurdy.com/gregor/ltag/
helpful in guessing CVS tags.  It reduces the search space considerably.
(It might not help much when matching up different modules, though...)

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

It looks like the name arm-uclinux is in use, and makes more sense than
arm-elf, at least to me; see
http://gcc.gnu.org/ml/gcc-patches/2000-01/msg00216.html
http://sources.redhat.com/ml/binutils/2001-10/msg00564.html
http://www.uclinux.org/pub/uClinux/archive/5837.html
I'd expect m68k-uclinux to also be popular?

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 :-)

 > and I've read through your docs.
> Now I just need to port rlogind to uClinux...

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.

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...
- Dan


-- 
Dan Kegel
http://www.kegel.com
http://counter.li.org/cgi-bin/runscript/display-person.cgi?user=78045