62774 – distcc 2.17 client causes "ERROR: Connect timeout"

Bug 62774 - distcc 2.17 client causes "ERROR: Connect timeout"

Summary: distcc 2.17 client causes "ERROR: Connect timeout"

Status:	RESOLVED FIXED

Alias:	None

Product:	Gentoo Linux
Classification:	Unclassified
Component:	New packages (show other bugs)
Hardware:	All All

Importance:	High normal (vote)
Assignee:	Lisa Seelye (RETIRED)

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2004-09-03 19:08 UTC by Colin Macdonald
Modified:	2004-10-12 13:25 UTC (History)
CC List:	0 users

See Also:
Package list:
Runtime testing required:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

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)