Author Topic: "semi" Native Compilation With Distcc (Read 35568 times)

xjqian · « **Reply #30 on:** October 31, 2006, 04:46:17 am »

I have problem with distcc to talk with distccd on my debian machine over wifi. Anybody know how to check if port 3263 is open?

InSearchOf · « **Reply #31 on:** October 31, 2006, 10:23:04 am »

It shouldnt be closed on your Z... I would say check your debian box...

Late

xjqian · « **Reply #32 on:** November 01, 2006, 11:17:48 pm »

Quote

It shouldnt be closed on your Z... I would say check your debian box...

Late
[div align=\"right\"][a href=\"index.php?act=findpost&pid=145215\"][{POST_SNAPBACK}][/a][/div]

@debain: netstat -an
tcp6 0 0 :::3632 :::* LISTEN
which is the default port according to the distccd man page. Somebody mentioned port 3263 in an earlier post. I want to make sure my Zaurus is using the same port.

xjqian · « **Reply #33 on:** November 06, 2006, 04:25:28 am »

Debain box - lan
Zaurus - wifi ping each other without problem.

I followed the instruction through, but I've got the following error on my z

Code: [Select]

distcc[9697] (dcc_writex) ERROR: failed to write:Connection reset by peer
distcc[9697] (dcc_build_somewhere) Warning: failed to distribute to 192.168.x.x, running locally instead

Anybody know how to check up my set up?

Edit: SOLVED!
I forgot that I set distccd to start at boot-up with a bad allowed ip. Then I didn't stop/restart distccd. No wonder distccd --daemon command didn't work. Now happy compiling.

telemetric_au · « **Reply #34 on:** May 08, 2007, 09:38:37 pm »

for anyone else having problems initialising the sdk, you may be helped here;

https://www.oesf.org/forums/index.php?showt...runsdk\.sh

telemetric_au · « **Reply #35 on:** June 23, 2007, 04:19:17 am »

just tried this out finally , and it is great... i should have been using it for a while back....

thanks to the author, ill post my details later.

News:

Author Topic: "semi" Native Compilation With Distcc (Read 35568 times)