| 1 |
> Both machines contain "distcc" in FEATURES. It's not using |
| 2 |
> -march=native. I've tried various -jN values with no real difference |
| 3 |
> in performance. |
| 4 |
|
| 5 |
only client (your laptop) machine should be distcc featured. for server |
| 6 |
(desktop) that feature is useless |
| 7 |
|
| 8 |
> On the desktop, /etc/conf.d/distcc contains (among other things): |
| 9 |
> DISTCCD_OPTS="${DISTCCD_OPTS} --allow 192.168.0.0/24" |
| 10 |
> DISTCCD_OPTS="${DISTCCD_OPTS} --listen 192.168.0.100" |
| 11 |
|
| 12 |
this is server distcc daemon configuration, one just instructs daemon on what |
| 13 |
network interface to listen for incoming connections (interface with ip |
| 14 |
192.168.0.100 in your case) and filter incoming distcc connections by source |
| 15 |
address: allow only those coming from local network machines with ip addresses |
| 16 |
192.168.0.1 to 192.168.0.254 |
| 17 |
|
| 18 |
then distccd have to be started: /etc/init.d/distccd start |
| 19 |
|
| 20 |
> And /etc/distccd/hosts contains: |
| 21 |
> 192.168.0.0/24 |
| 22 |
|
| 23 |
this file configures distcc client behavior (actually the configuration can be |
| 24 |
complex, see distcc man page for details), but in trivial case (for home |
| 25 |
computing) it might look like: |
| 26 |
|
| 27 |
192.168.0.100/6 127.0.0.1/1 |
| 28 |
|
| 29 |
e.g the client is able to send up to 6 distcc jobs to 192.168.0.100 and limit to |
| 30 |
one job at local machine. client's /etc/make.conf has to have distcc feature |
| 31 |
enabled (FEATURES="distcc"). surely you can play with job distribution rules |
| 32 |
around the network. `distcc --show-hosts` command displays what you configured. |
| 33 |
the number of cuncurrently running jobs (-j flag) has to be not less than sum of |
| 34 |
local and remote jobs |
| 35 |
|
| 36 |
i had noticed that distcc is peevish about CFLAGS: these should be compatible on |
| 37 |
both client and server. in my case i made these similar on both machines (laptop |
| 38 |
is core2duo and desktop is core2quad; both are running amd64 arch) |
| 39 |
|
| 40 |
yet another way to install packages on weak notebook running it on the same arch |
| 41 |
as desktop runs, - is to create binaries at powerful machine (while emerging or |
| 42 |
with quickpkg utility) and share $PKGDIR with laptop |
| 43 |
|
| 44 |
hth |
Archives