[distcc] I don't get it working on an Terminal Server envirmoment

Martin Pool mbp at sourcefrog.net
Mon Mar 7 11:32:39 GMT 2005


Torsten wrote:
> Good morning,
> 
> since last friday I'm trying to get distcc running within an Terminal 
> Server enviroment (LTSP-4.1).
> LTSP does not provide an compiler, and on its ML its said to use distcc. 
> So I downloaded distcc to the Terminal Server (running SuSE 9.2), and 
> compiled/installed it.
> Right now I'm starting distccd via command line, using:
>   /usr/local/bin/distccd --daemon --listen 192.168.10.1 --allow \
>   192.168.10.0/24 --log-file /tmp/distccd.log --user nobody
> ps ax tells me ther are 4 distccd processes ... ok so far.
> I also wrote this line in /etc/exports:
>   /usr/local/bin 192.168.10.0/255.255.255.0 \
>   (async,insecure,no_root_squash,rw)
> 
> As there's no compiler within the Thin Clients enviroment 
> (/opt/ltsp/i386) I'm not sure what to do now ... I copied 
> /usr/local/bin/* to /opt/ltsp/i386/usr/local/bin/, and created an hosts 
> file there, with the content:
>   192.168.10.1
>   192.168.10.1:/usr/local/bin

What is the path there for?

> But as soon as I start compiling (./configure) any program I get errors, 
> like:
>   checking for gcc ..... no
>   checking for cc ...... no

So, in the first place: can you run gcc without distcc from inside the 
client environment?

Secondly, try compiling a simple c file using distcc with 
DISTCC_VERBOSE=1 set.

-- 
Martin


More information about the distcc mailing list