[distcc] timeout on distcc build of kde 3.3.0 isn't actually a timeout

Hamish Greig hgreig at bigpond.net.au
Wed Sep 15 07:58:25 GMT 2004

On Wed, 15 Sep 2004 08:16, Luke Kenneth Casson Leighton wrote:
> hi,
> kde has a habit of creating a #include file with the entire set of
> auto-generated cpp files in it.
> this results in several minute builds as the /tmp/xxxx.s assembly file
> climbs in some cases to well over 8mbytes in size.
> distcc bitches about it with a "timeout" error.
> how can this be stopped?
> ta,
> l.

don't pass --enable-final to configure and then it shouldn't do that. 
I thought the same thing is said in the distcc FAQ, but anyway I know from my 
experience with KDE compiles, --enable-final means distcc is distributing 
250MB+ files to remote servers, so if you have less than a 100MB network the 
time you save on actual  compiling you lose on transferring those huge files. 
I haven't noticed any performance or stability differences either with or 
without --enable-final so now I just don't use that in my configure line.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.samba.org/archive/distcc/attachments/20040915/0e6e9e70/attachment.bin

More information about the distcc mailing list