By: Gemon

Gemon — Thu, 03 Feb 2011 22:22:47 +0000

mmm, just succeded in using distcc on my linux box at home (pentium 2 350MHz) and my virtual archlinux host on my core i5 work laptop…
All in all it’s pretty easy. That’s what I did (both run archlinux, but I didn’t follow the wiki…just plain old manual compilation):

- pacman -S distcc on all hosts
- on the ‘big’ one (the virtual host laptop, hostname vbox), login as a normal user and do:
# distcc -daemon –allow 192.168.0.0/24
- on the ‘small’ one (the p2-350), just do
# export DISTCC_HOSTS=’localhost vbox’
- cd to sources (I used as an example util-linux-ng 2.18 sources)
- ./configure (usually)
# make -j8 CC=distcc

if everything works the client (where you started the make) won’t tell you anything if it is correctly distributing compilation work units. But you can easily see them by running htop on the other host…

have fun!
Gemon

By: chive

chive — Mon, 03 Jan 2011 14:22:49 +0000

You can always replace /usr/bin/gcc symlink with one pointing to /usr/bin/distcc, this worked in Slackware for me and should fool system properly… If other machines are offline it will compile locally instead anyway.
For manual compiling of various packages I also simply exported CC variable like this: ‘export CC=/usr/bin/distcc’
Never used anything to manage ports though… I prefer to keep it in my head
Does it work if you compile things without prt-get or pkgmk?
Once you manage to get it working you’ll never try to compile things on pentium alone again, I had my Toshiba 440CDT (p133 mmx) coupled with old pentium4 2.6 and it did wonders

Good luck!

Comments on: distcc: Still no luck

By: Gemon

By: chive