[Cook] Distcc and Cook

[Jerry Pendergraft]

On Tue, 15 Feb 2005, Simon Clift wrote:

> On Tue, 2005-02-15 at 09:22 -0600, Jerry Pendergraft wrote:
> > OK then the simple solution is to do
> >  parallel_rsh = distcc_wrap;
> > For a longer explanation .. in case it helps.
> 
> Thanks for that explanation.  I'd been hoping to avoid
> doing a cook_rsh wrapper since as far as cook is
cook_rsh is very much more than a wrapper. It negotiates 
remote command capabilities, loads etc and balances jobs
over a network of machines.

> concerned, all of the processes should appear to be
> executing on the localhost.  DistCC pulls together
Not really - cook only does the dependency checking and calculates
the necessary commands to run on other machines.
> what the compilation needs, pipes it over to the
> machine where the compilation is to be done, then
> gets the compiled file back over a pipe.  The box
Do you really mean "gets everything needed"?
Seems like that could take longer than the actual compile.
Plus, considering includes etc be very tricky.
And, of course, would not deal with multi-architecture needs which
actually requires the remote machine be of the required architecture.

> doing the compilation otherwise has no access to 
> the files of the originating machine.
> 
> I hit some troubles with shell quoting on the wrapper, 
> and eventually just tried ssh for everything, but again
> only one thread at a time started, even though 8 should
> have (-par 8).
> 
> Then I found my problem: I'd wrapped most of my compiles
> in [shell] because of some parameter quoting hassles
> I'd had a long time ago.  Removing that seems to have
> gotten things going.
> 
> Now, if only my admins would update our big parallel
> box from gcc-2.95.0... :-(
> 
> Thanks again for your help.
> -- Simon
> 
>