On Sunday 03 April 2005 13:18, Andrew de Quincey wrote: > On Sunday 03 April 2005 11:35, Stuart Longland wrote: > > Andrew de Quincey wrote: > > > On Sunday 03 April 2005 03:10, Andrew Gaffney wrote: > > >>Andrew de Quincey wrote: > > >>>Hi, I hope this is the correct place to send this. > > >>> > > >>>I have setup distcc in my network. Most of the hosts are i686, but one > > >>> of them is x86_64. I wish to distribute tasks to the i686 machines > > >>> from the x86_64 machine. This involves installing a cross compiler on > > >>> the i686 machines for x86_64 tasks. Crossdev is overkill for this - I > > >>> don't actually _need_ glibc and the like on the client machines for a > > >>> simple distcc environment. It really adds to the upgrade time when > > >>> emerge sync; emerge worlding. > > >> > > >>crossdev -s1 -t <x86_64 CHOST> > > > > > > According to the docs, that doesn't compile a c++ compiler: > > > > > > -s1, --stage1 Build a C compiler (no libc/C++) > > > > And guess what... no libc... no c++. If you require a C++ compiler, > > then might I suggest making a µClibc-based toolchain? µClibc is just a > > little smaller than it's GNU cousin, and so shouldn't occupy much space. > > I have it running right now with *no* libc and g++. There is no reason to > need a libc, apart from the fact that you cannot confiure g++ to build > without patching it. I have just distcc compiled kdlibs with this > configuration. > > Have you actually tried the patch? This is precisely what it does - g++ > with no libc. > > The files installed with the patch are in the attached file. I could > perhaps trim it more - there is no need for the include files either with > distcc.
Oh - the only cross packages I have installed for a fully working distcc are: cross-x86_64-pc-linux-gnu/binutils * cross-x86_64-pc-linux-gnu/gcc * Where gcc contains just the files I listed previously. -- gentoo-dev@gentoo.org mailing list
