Re: buildworld fails with distcc, buildkernel works fine though

[YONETANI Tomokazu <qhwt+dfly@xxxxxxxxxx>]

On Thu, Oct 14, 2004 at 03:38:21PM +0200, Simon 'corecode' Schubert wrote:
> >- the system clock on each node must be in sync or the make program
> >  gets screwed.
> 
> if you use distcc, you just distribute the compiling, not even the 
> preprocessing, so make isn't an issue here.
>
> >- you probably have to install exact same version of OS on each
> >  node, same make.conf file, and the same environment variables.
> >  diffent configurations produce diffent outputs, so mixing them up
> >  will result in unexpected errors.
> 
> that's true for CCVER and OBJFORMAT_PATH, all other variables shouldn't 
> be used when just compiling

<blush>
Right, what was in my mind was something not what distcc actually is...

> 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).