DistCC on MIPS & Cross compillers

[Redhatter]

Hi,
One idea hit me recently.... I have sitting here an SGI Indy (which has been doing an emerge -UD world for a couple of days now, up to package 24 of 48) and a Gateway Microserver.

To use distcc between them, would a simple kernel cross compiller do the trick? Or do I need to coax crossdev into producing the whole kit?

I managed to get qube (microserver) to do a mipsel->mips cross compiller (kernel only, no glibc), and I hope to get the corresponding cross compiler going on indy. Do I need to muck around with glibc to use distcc between these boxes?
_________________
Stuart Longland (a.k.a Redhatter, VK4MSL)
I haven't lost my mind - it's backed up on a tape somewhere...

Gentoo/MIPS Cobalt developer, Mozilla herd member.

[Kumba]

Hrmm, well, in most cases, you only need the kernel compiler, because distcc only does object compiling on the remote distcc system. No linking is involved, so glibc is never needed (all linking is done on the original system). The problem is if you need g++ to compile c++ programs. In order for distcc to properly distribute c++ source files, the remote system will need g++, and this requires glibc. An unfortunate requirement, but eh, welcome to the dark, arcane world of cross-compilers.

I'm finally merging some long overdue patches into crossdev and hope to post a 0.5 version in time that may help kill off some bugs (and introduce some new ones, as is usually the case).


--Kumba
_________________
"The past tempts us, the present confuses us, the future frightens us. And our lives slip away, moment by moment, lost in that vast, terrible in-between."
--Emperor Turhan, Centauri Republic