[distcc] Re: Announcing distccKNOPPIX

[Martin Pool]

On  8 Jul 2003, Alexandre Oliva <oliva at lsd.ic.unicamp.br> wrote:

> ~/.distcc/hosts doesn't quite cut it for me.  Because of the way I use
> cross, native or cross-native (*) toolchains, the same set of hosts
> may or may not work, depending on what CC I'm using, for example, the
> system's GCC, that varies depending on the exact version of Red Hat
> Linux, sometimes betas or even rawhide I'm running on each of my
> hosts; or GNU Pro natives or crosses that work identically on all of
> them.  It would be nice if I could express this kind of dependency on
> in DISTCC_HOSTS or ~/.distcc/hosts somehow.

What about being able to set

  DISTCC_HOSTS=~/.distcc/ia64-hosts

and then have a program produce that file? 

It ought to be straightforward to add support to the host syntax for
including files containing lists.

> The need for per-host validation of CC compatibility reminded me of an
> issue I had when trying to play with distcc over (fsh/)ssh (fsh would
> cut down connection set up time) was that, since it wouldn't set up
> the PATH like a login session would, it would end up not finding
> soft-links to compilers that I had in my PATH on the build machine,
> but that would be correctly found in the distccd environment when I
> started distccd in a login session.  I couldn't find a clean solution
> for this, so I ended up giving up on distcc over ssh :-(  Anyway, if
> distcc (or distccd?) could source a script to set up an environment
> before starting the compiler on the remote host, this would help.
> ~/.distcc/env?

What about ~/.ssh/environment?

> Alternatively, it could support mapping compiler pathnames to
> host-dependent full pathnames, but this doesn't sound as useful or
> generic as a server-side env setting.

I think ccontrol will eventually do that.

-- 
Martin