[distcc] distcc-over-ssh!

[Wayne Davison]

On Tue, Apr 01, 2003 at 09:06:34AM +1000, Martin Pool wrote:
> distcc over SSH is now working in CVS!

It's nice to see at least one announcement that isn't an April-fools
joke.  I'm starting some testing of this, and so far my very simple
tests have been successful.  (I'm testing CVS + all my remaining
patches.)

One thing I noticed (in both the ssh and non-ssh version) is that distcc
says that to be executing "gcc -E" twice.  Should that be happening?  I
haven't noticed this before, but that doesn't mean it's new.  I'm just
running "distcc gcc -c foo.c" with a single remote host in DISTCC_HOSTS.

distcc[17903] (dcc_recursion_safeguard) safeguard level=0
distcc[17903] (dcc_trace_argv) scanning arguments: gcc -c foo.c
distcc[17903] (dcc_scan_args) found input file "foo.c"
distcc[17903] (dcc_scan_args) no visible output file, going to add "-o foo.o" at end
distcc[17903] compile from foo.c to foo.o
distcc[17903] (dcc_parse_hosts) found tcp token "home:4269"
distcc[17903] (dcc_lock_host) got cpu lock on home slot 0
distcc[17903] (dcc_lock_host) got xmit lock on home slot 0
distcc[17903] (dcc_trace_argv) result: gcc -c foo.c
distcc[17903] (dcc_trace_argv) forking to execute: gcc -E foo.c
distcc[17903] (dcc_spawn_child) child started as pid17904
distcc[17903] (dcc_trace_argv) result: gcc -c foo.c -o foo.o
distcc[17903] exec on home: gcc -c foo.c -o foo.o
distcc[17904] (dcc_inside_child) setting safeguard: _DISTCC_SAFEGUARD=1
distcc[17904] (dcc_recursion_safeguard) safeguard: 1
distcc[17904] (dcc_recursion_safeguard) safeguard level=1
distcc[17904] (dcc_set_path) setting PATH=...trimmed...
distcc[17904] exec on localhost: gcc -E foo.c
distcc[17904] (dcc_trace_argv) forking to execute: gcc -E foo.c
distcc[17905] (dcc_inside_child) setting safeguard: _DISTCC_SAFEGUARD=2
distcc[17904] (dcc_spawn_child) child started as pid17905

..wayne..