I'm trying to get distccd on an x86 Mandrake 8.1 box to work, and every time the "client" calls on it, a single distccd process immediately pegs the system.
I've tried using --verbose and --no-detach, and with/without --user. I get -zero- debugging info(not even a "connection from" message), but when I kill distccd, I get some messages on the 'client' side about loosing the connection from that system.
The 'client' is a gentoo system, using distcc 2.10. I was running 2.11 on the Mandrake system, but downgraded to 2.10 to see if it was a version incompatibility- it wasn't. I eliminated portage from the equation by running some manual compiles.
Only thing I can think of is that Mandrake uses a funky system of links to allow you to switch compilers easily. /usr/bin/gcc links to /etc/alternatives/gcc, which in turn links to wherever your favorite gcc is(for example, /usr/local/bin/gcc). This works fine on the system doing 'normal' compiles, but I wonder if this setup is giving distcc a conniption?
Any suggestions would be greatly appreciated.
Thanks, Brett
__ distcc mailing list http://distcc.samba.org/
To unsubscribe or change options: http://lists.samba.org/cgi-bin/mailman/listinfo/distcc
