[distcc] Two incompatibilities between distcc & C++/configure

[Martin Pool]

On 30 Jan 2003, Lezz Giles <lgiles at starentnetworks.com> wrote:
> I've been using distcc to speed up builds of our product,
> and in general it works really well.  However I found two
> incompatibilities (best word I could find):
> 
> C++ has a pragma "implementation" which uses the source
> filename to decide what to do (we're usig GCC 3.0.3, but
> I think this is true in more versions than just this one),
> and since distcc changes the filename on the server that
> is compiling the file, the resulting object file is wrong.

So it really uses the input filename rather than whatever's specified
by the #line directives?  That's a bit wierd.

> And our zlib configure script checks the C compiler by
> checking that stdout and stderr are both empty; when I
> was building it one of the remote servers was not running its
> distccd properly, so I got an ERROR: message about not
> being able to connect - this message convinced the configure
> script that gcc wasn't working.  At least there's a workaround
> for this one - set CCDIST_LOG to /dev/null.

Yes, this is already in the manual I think, though perhaps not clearly
enough.

> For the C++ error it would be nice if the server used the
> same filename as the client.  I can't see any downside except
> that you'd need to put the temporary files into their own directories
> rather than having everything at the top level.

OK.

> Thanks for a great tool!

You're welcome.  Thanks for the comments.

-- 
Martin