[distcc] Re: distcc control methods

Wayne Davison wayned at users.sourceforge.net
Tue Jul 8 08:37:25 GMT 2003

On Tue, Jul 08, 2003 at 09:42:51AM +0200, Markus Werle wrote:
> Could You give an example?

The oft-mentioned example is KDE (due to its current libtool script).
There are others as well, but I'll never run into them because I've
never controlled distcc by munging CC (if you're curious, search through
the gentoo bugzilla or the gentoo forums -- people mention other
packages that used to fail back before portage started using the
masquerade dir setup).

> If You dislike setting CC, how about a shell script /opt/my_distcc/bin/cc
> which calls
> distcc --verbose --hosts=\"mach:9999\" --disable-fallback --compiler=icpc
> and PATH=/opt/my_distcc/bin:$PATH

That's a bad way to go because (1) you have to have a separate set of
fake-compiler scripts for every user to set their own options, (2) you'd
need to script PATH-munging or use an absolute PATH to the compiler
(requiring the compiler to be in the same bin dir on all machines in the
latter case), (3) to change the options would require you to edit/change
all the scripts, and (4) it's slightly less efficient (with an extra
shell exec before distcc runs).  No thanks.

The masquerade dir of symlinks is the best way I've seen to control
distcc with the greatest portability and flexibility.  Yes, if setting
CC and CXX was 100% reliable, your arg-parsing solution would probably
be a good way to go, but unfortunately it sometimes fails, so I prefer
to avoid it.


More information about the distcc mailing list