There were some changes to the tool chain which means that distcc wont work across different x86 archs (e.g., athlon and pentium) and the devs wont change it (marked as WONT FIX on the bug).
The workaround is to add CC-gcc and CXX=g++ to make .conf on the client, however this may break other things, not to mention that it isnt currently working for me with gcc3.4 (multiple toolchain scenario). This is a real pita as distcc is most useful when using a fast modern machine supporting slow older machines, which usually means different x86 archs. If you use distcc, turn logging on on the server and make sure its really working, and not going through the motions and silently erroring off. see the distcc buglist (#84942) and I think some forum posts for the gory details ... BillK On Thu, 2005-06-16 at 12:56 -0400, michael higgins wrote: > I have a couple of questions about using distcc. I have two machines. One is > significantly faster than the other, both x86 (pentium 2 and amd athlon-xp). > > I've followed the http://www.gentoo.org/doc/en/distcc.xml instructions for > configuring portage to use distcc. Should I need to continue with the > instructions for "working with automake"? > > Also, how do I tell the faster machine to just use it's own power and not > attempt to use the slower one? > > I tried so far, getting distccd running on both machines, each distcc-config > --set-hosts has one IP entry, that of the other machine. Is this right? > > I ran distcc-gnome and saw no activity reported on the faster machine when > emerging something on the slower one. So, it would seem it's not working. > > Can anyone give me some hints? The manpage for distcc doesn't seem (to me) to > be much related to the gentoo how-to... '-) > > TIA, > > -- > |\ /| | | ~ ~ > | \/ | |---| `|` ? > | |ichael | |iggins \^ / > michael[dot]higgins[at]snet[dot]net -- William Kenworthy <[EMAIL PROTECTED]> Home! -- gentoo-user@gentoo.org mailing list
