It is normal that the gcc command line on the server will not exactly
match the distcc command line on the client. Distcc will munge the
command line a bit.
On 04/07/2009, at 10:36 PM, psfblair <cir...@phobot.net> wrote:
Just in case someone on the Internet is hunting around for a
solution to this
problem--I had a very similar one on Gentoo Linux. Here's what I did
to
solve it:
1. netstat -c --inet showed me active internet connections. I could
see both
on the server and on the client that requests were coming into the
server
but nothing was going out.
2. I restarted distccd with the option --verbose (and --log-file) to
get an
idea of what was happening on the server.
In my case, what was happening was that the command line for gcc on
the
server did not match what was being requested on the client. YMMV of
course.
--
View this message in context:
http://www.nabble.com/Host-connection-seems-to-fail-on-W32-system-%28Cygwin%29-tp7344631p24337838.html
Sent from the Distcc mailing list archive at Nabble.com.
__
distcc mailing list http://distcc.samba.org/
To unsubscribe or change options:
https://lists.samba.org/mailman/listinfo/distcc
__
distcc mailing list http://distcc.samba.org/
To unsubscribe or change options:
https://lists.samba.org/mailman/listinfo/distcc