I'm trying to get distcc running to do a distributed buildworld. As a test, I installed FreeBSD 13.2 amd64 on 2 Qemu virtual machines. Both are connected to 2 tap devices in a network bridge. They can ping the host and eachother. The ip's of these machines are 192.168.2.5 and 192.168.2.7. The latter is the system where the buildworld will be started. The other has to contribute to that by taking over compiler threads.
I can't find any complete documentation, or at least not what is to the point and works. Various AI machines can't solve it either, probably because of this.
Since the daemon has to run on all participating systems, it's also not clear to me what are called client and server respectively and what even is the difference...
On the client (the system where the buildworld will be executed?), I now have rc.conf settings:
On the server, I have rc.conf setting distcc_enable="YES", and /etc/make.conf with:
On the server, shell variable DISTCC_HOSTS="192.168.2.5" is set.
Now, nothing happens remotely when running a buildworld. What am I missing?
I can't find any complete documentation, or at least not what is to the point and works. Various AI machines can't solve it either, probably because of this.
Since the daemon has to run on all participating systems, it's also not clear to me what are called client and server respectively and what even is the difference...
On the client (the system where the buildworld will be executed?), I now have rc.conf settings:
Code:
distcc_enable="YES"
distcc_flags="--allow 192.168.2.7 --listen 192.168.2.5"On the server, I have rc.conf setting distcc_enable="YES", and /etc/make.conf with:
Code:
CC=distcc
CXX=distccOn the server, shell variable DISTCC_HOSTS="192.168.2.5" is set.
Now, nothing happens remotely when running a buildworld. What am I missing?