by Philoo » Wed Oct 03, 2012 7:18 pm
a couple of basics:
1/ if cross compiling make sure that either the folder where your cross compiler sits is first in $PATH (I think I saw that in the wrong order) and/or explicitely masquerade the compilers , as per the man page:
$this->bbcode_second_pass_quote('', 'M')ASQUERADING
The basic idea is to create a "masquerade directory" which contains links from the name of the real compiler to the distcc binary. This directory is inserted early on the PATH, so that calls to the compiler are intercepted and distcc is run instead. distcc then removes itself from the PATH to find the real compiler.
For example:
# mkdir /usr/lib/distcc/bin
# cd /usr/lib/distcc/bin
# ln -s ../../../bin/distcc gcc
# ln -s ../../../bin/distcc cc
# ln -s ../../../bin/distcc g++
# ln -s ../../../bin/distcc c++
this is to be done the server(s)
2/ distccd processes are actually running on the server (ps awx | grep distccd)
3/ as a regular user (stricto sensu you also can as root but it's not adviseable) you can run distccd in non-daemon, verbose/debug-output-on-the console mode
4/ make sure your port is open $this->bbcode_second_pass_code('', 'nmap -p 3632 distcc.server.ip') and you are looking a the right host (it took me a couple hours to figure that I was sending jobs to my VM host instead of the guest the first time)