Re: buildworld fails with distcc, buildkernel works fine though

["Simon 'corecode' Schubert" <corecode@xxxxxxxxxxxx>]

On 14.10.2004, at 18:09, YONETANI Tomokazu wrote:
> > Thinking about it: how about
> >
> > 1. distcc'ing the tools stage. this will result in a fresh gcc.
> > 2. distributing the compiler (or all the tools) to all nodes.
> > 3. using this compiler (now guarranteed to be the same everywhere) to
> > compile world. hostcc will stay on host, of course.
> Hmm, there are many places where ${CC} is used for other purpose than 
> as a
> compiler, and ${CC} will collect information from remote nodes rather 
> than
> the host node, if you use distcc unconditionally. That means you may 
> also
> have to share the same tree on each node, or else you have to look for 
> each
> usage of ${CC} and change it to not use distcc(or look for ${CC} and 
> change
> them only if it's safe to use distcc).

distcc is actually that intelligent to understand what the caller is 
trying to do. and only if a file needs to be compiled, it runs the 
compilation on a remote host. everything else, including preprocessing 
is done locally.

cheers
  simon

--
/"\
\ /
 \     ASCII Ribbon Campaign
/ \  Against HTML Mail and News

Attachment: PGP.sig
Description: This is a digitally signed message part