Bug 62774

Summary:	distcc 2.17 client causes "ERROR: Connect timeout"
Product:	Gentoo Linux	Reporter:	Colin Macdonald <cbm>
Component:	New packages	Assignee:	Lisa Seelye (RETIRED) <lisa>
Status:	RESOLVED FIXED
Severity:	normal
Priority:	High
Version:	2004.2
Hardware:	All
OS:	All
Whiteboard:
Package list:		Runtime testing required:	---

Description Colin Macdonald 2004-09-03 19:08:44 UTC

Hi,

Using distcc-2.17-r1 on my two systems causes lots of "ERROR: Connect timeout" errors dies.

This is an upstream bug which is described here:

http://archive.netbsd.se/?list=distcc&a=2004-08&mid=275438

A solution is to use distcc-2.16 on the *client* machine (or probably on both will work too but I haven't confirmed that.)

At the very least, I'd suggest a note in the 2.17-r* ebuilds to make sure they never enter x86.  Or perhaps even hardmask them and make 2.16 the current distcc in ~x86.

Comment 1 Colin Macdonald 2004-09-03 19:09:25 UTC

First line should say "... and the build process dies".  Sorry

Comment 2 Colin Macdonald 2004-10-12 13:25:49 UTC

Fixed in 2.18: from the changelog:

distcc-2.18  "Billionaires on stilts"  2004-10-12

  BUG FIXES:

    * Fix longjmp() bug that can cause distcc to crash when a timeout
      elapses.

Suggest we get 2.17 out of the tree ASAP (just make sure it never goes stable)