/[gentoo]/xml/htdocs/doc/en/distcc.xml
Gentoo

Diff of /xml/htdocs/doc/en/distcc.xml

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

Revision 1.3 Revision 1.21
1<?xml version='1.0' encoding="UTF-8"?> 1<?xml version='1.0' encoding="UTF-8"?>
2<!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> 2<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
3<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/distcc.xml,v 1.3 2003/09/08 08:09:02 blubber Exp $ --> 3<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/distcc.xml,v 1.21 2004/07/28 14:38:25 swift Exp $ -->
4
5<!--
6 Synchronised with rev 1.15 on
7 http://www.thedoh.com/viewcvs/distcc/html/distcc.xml
8-->
4 9
5<guide link="/doc/en/distcc.xml"> 10<guide link="/doc/en/distcc.xml">
6 11
7<title>Gentoo Distcc Documentation</title> 12<title>Gentoo Distcc Documentation</title>
8 13
9<author title="Author"> 14<author title="Author">
10 <mail link="lisa@gentoo.org">lisa@gentoo.org</mail> 15 <mail link="lisa@gentoo.org">Lisa Seelye</mail>
16</author>
17
18<author title="Editor">
19 <mail link="vapier@gentoo.org">Mike Frysinger</mail>
20</author>
21
22<author title="Editor">
23 <mail link="erwin@gentoo.org">Erwin</mail>
24</author>
25
26<author title="Editor">
27 <mail link="swift@gentoo.org">Sven Vermeulen</mail>
28</author>
29
30<author title="Editor">
31 <mail link="pylon@gentoo.org">Lars Weiler</mail>
11</author> 32</author>
12 33
13<author title="Reviewer"> 34<author title="Reviewer">
14 <mail link="swift@gentoo.org">swift@gentoo.org</mail>
15</author>
16
17<author title="Reviewer">
18 <mail link="blubber@gentoo.org">blubber@gentoo.org</mail> 35 <mail link="blubber@gentoo.org">Tiemo Kieft</mail>
19</author> 36</author>
20 37
38<abstract>
39This document serves as a HOWTO for using distcc with Gentoo.
40</abstract>
41
42<!-- The content of this document is licensed under the CC-BY-SA license -->
43<!-- See http://creativecommons.org/licenses/by-sa/1.0 -->
44<license/>
45
21<version>1.1</version> 46<version>1.7.2</version>
22<date>September 08, 2003</date> 47<date>July 28, 2004</date>
23 48
24<abstract>This document serves as a HOWTO for using distcc with Gentoo.</abstract>
25
26<chapter> 49<chapter>
27 <title>Introduction</title> 50<title>Introduction</title>
28 <section> 51<section>
29 <title>What is distcc?</title> 52<title>What is distcc?</title>
30 <body> 53<body>
31 <p>Distcc is a program designed to distribute compiling tasks across a network to participating hosts. It is comprised of a server, <c>distccd</c> and a client program, <c>distcc</c>. Distcc can work transparently with <uri link="http://ccache.samba.org">ccache</uri> and Portage with a little set up.</p> 54
55<p>
56Distcc is a program designed to distribute compiling tasks across a network to
57participating hosts. It is comprised of a server, <c>distccd</c> and a client
58program, <c>distcc</c>. Distcc can work transparently with <uri
59link="http://ccache.samba.org">ccache</uri> and Portage with a little work.
60</p>
61
32 </body> 62</body>
33 </section> 63</section>
34
35 <section> 64<section>
36 <title>Dependancies</title> 65<title>Using distcc to bootstrap</title>
37 <body> 66<body>
38 <pre caption="Distcc Dependancies"> 67
39&gt;=sys-apps/portage-2.0.46-r11 68<p>
40&gt;=sys-devel/gcc-config-1.3.1 69If you are planning on using distcc to help you bootstrap a Gentoo installation,
41&gt;sys-apps/shadow 70make sure you read the part on <uri link="#bootstrapping">Using distcc to
42<codenote>(As of version 2.8) And the following optional dependancies when you have <c>gtk</c> in your <c>USE</c> flags</codenote> 71Bootstrap</uri> which is situated further down in this document.
43&gt;=x11-libs/gtk+-2.2.1 72</p>
44 </pre> 73
45 </body> 74</body>
46 </section> 75</section>
47</chapter>
48
49<chapter> 76</chapter>
77
78<chapter>
50 <title>Setup</title> 79<title>Setup</title>
51 <section> 80<section>
81<title>Dependencies</title>
82<body>
83
84<p>
85To start off with, to use Distcc all of the computers on your network need to
86have the same GCC versions. Mixing 3.3.x (where the x varies) is okay, but
87mixing 3.3.x and 3.2.x is not: your programs <b>will</b> have errors in it.
88</p>
89
90</body>
91</section>
92<section>
93<title>Installing Distcc</title>
94<body>
95
96<p>
97There are a couple of options you should know about before you start
98installing distcc.
99</p>
100
101<p>
102Distcc ships with a graphical monitor to monitor tasks that your computer is
103sending away for compilation. If you use Gnome then put 'gnome' in your USE
104flags. However, if you don't use Gnome and would still like to have the
105monitor then you should put 'gtk' in your USE flags.
106</p>
107
108<pre caption="Installing distcc">
109# <i>emerge distcc</i>
110</pre>
111
112</body>
113</section>
114<section>
52 <title>Setting up Portage to use Distcc</title> 115<title>Setting up Portage to use Distcc</title>
53 <body> 116<body>
54 <p>Setting up distcc is very easy to do with Portage. Follow these simple steps on each computer you want to use distcc on:</p> 117
118<p>
119Setting up distcc is easy to do with Portage. Execute the following steps on
120each system that should participate in the distributed compiling:
121</p>
122
55 <pre caption="Integrating Distcc and Portage"> 123<pre caption="Integrating Distcc and Portage">
56# <i>emerge distcc</i> 124# <i>emerge distcc</i>
57# <i>nano -w /etc/make.conf</i> 125# <i>nano -w /etc/make.conf</i>
58<codenote>Edit your FEATURES flags to include &quot;distcc&quot;</codenote> 126<comment>(Set N to a suitable number for your particular setup)</comment>
127<comment>(A common heuristic strategy is twice the number of CPUs + 1)</comment>
128MAKEOPTS="-jN"
129<comment>(Add distcc to your FEATURES variable)</comment>
130FEATURES="distcc"
59 </pre> 131</pre>
60 132
61 <p>Next you have to specify what hosts you want to use. To do this you can use the <i>distcc-config</i> command to set that list of hosts. Here is an example of some hosts that might be in your list:</p> 133<p>
134Next you have to specify what hosts you want to use. Use the
135<c>distcc-config</c> command to set the list of hosts. Here is an example of
136some hosts that might be in your list:
137</p>
138
62 <pre caption="Examples of host definitions"> 139<pre caption="Examples of host definitions">
63192.168.0.1 192.168.0.2 192.168.0.3 140192.168.0.1 192.168.0.2 192.168.0.3
64192.168.0.1/2 192.168.0.2 192.168.0.3/10 141192.168.0.1/2 192.168.0.2 192.168.0.3/10
65192.168.0.1:4000/2 192.168.0.2/1 192.168.0.3:3632/4 142192.168.0.1:4000/2 192.168.0.2/1 192.168.0.3:3632/4
66@192.168.0.1 @192.168.0.2:/usr/bin/distccd 192.168.0.3 143@192.168.0.1 @192.168.0.2:/usr/bin/distccd 192.168.0.3
144<comment>(There are also several other methods of setting up hosts. See the
145distcc manpage for more details.)</comment>
67 </pre> 146</pre>
68 <p>It may all look complicated, but in most cases a variant of line 1 or 2 will work. An explanation of each line is: Line 1 is just a space-delimited list of hosts that will use default everything. Line 2 is a list of hosts that specifies the maxmimum number of jobs (by use of the /N) to send that host at any given time (specified with the <c>/n</c>). Since most people won't be using lines 3 or 4, I'll <uri link="http://distcc.samba.org/man/distcc_1.html">point you to</uri> the distcc docs for more information.</p> 147
69 <p>A sample command to set the hosts (for line 1) is:</p> 148<p>
149It may all look complicated, but in most cases a variant of line 1 or 2 will
150work.
151</p>
152
153<ul>
154 <li>Line 1 is just a space-delimited list of hosts</li>
155 <li>
156 Line 2 is a list of hosts that specifies the maximum amount of jobs (by
157 defining the <c>/N</c> setting) to send that host at any given time
158 </li>
159</ul>
160
161<p>
162Since most people won't be using lines 3 or 4, I'll <uri
163link="http://distcc.samba.org/man/distcc_1.html">point you to</uri> the distcc
164docs for more information.
165</p>
166
167<p>
168For instance, to set the first line in the previous example:
169</p>
170
70 <pre caption="Sample command to set the hosts"> 171<pre caption="Sample command to set the hosts">
71# <i>/usr/bin/distcc-config --set-hosts "192.168.0.1 192.168.0.2 192.168.0.3</i> 172# <i>/usr/bin/distcc-config --set-hosts "192.168.0.1 192.168.0.2 192.168.0.3"</i>
72 </pre> 173</pre>
73 174
74 <p>The final step to integrating distcc into Portage is to re-open your <path>/etc/make.conf</path> and edit <c>MAKE_OPTS</c> to include <c>-jN</c> (where N is an integer). Typically you will want to set this to the total number of processors in your network plus one.</p> 175<p>
75 <pre caption="Final steps in make.conf"> 176Now start the distcc daemon on all the participating computers:
177</p>
178
179<pre caption="Starting the distcc daemon">
180<comment>(Add distccd to the default runlevel)</comment>
181# <i>rc-update add distccd default</i>
182<comment>(Start the distcc daemon)</comment>
183# <i>/etc/init.d/distccd start</i>
184</pre>
185
186</body>
187</section>
188<section>
189<title>Setting up Distcc to Work With Automake</title>
190<body>
191
192<p>
193This is in some cases easier than the Portage setup. What you have to do is
194update your <c>PATH</c> variable to include <path>/usr/lib/distcc/bin</path>
195in front of the directory that contains <c>gcc</c> (<path>/usr/bin</path>).
196However, there is a caveat. If you use ccache you have to put distcc after
197the ccache part:
198</p>
199
200<pre caption="Setting your path">
201# <i>export PATH="/usr/lib/ccache/bin:/usr/lib/distcc/bin:${PATH}"</i>
202</pre>
203
204<p>
205Then, as you would normally type <c>make</c>, you would type <c>make -jN</c>
206(where N is an integer). The value of N depends on your network and the types
207of computers you are using to compile. For me, I have a dual processor P3 and
208a K6-2/400 that compiles everything for my desktop (a 1200MHz Athlon
209Thunderbird) and I use -j5. Test your own settings to find the most
210performant number.
211</p>
212
213</body>
214</section>
215</chapter>
216
217<chapter>
218<title>Cross-Compiling</title>
219<section>
220<title>A Note on Cross-Compiling</title>
221<body>
222
223<p>
224Cross-compiling is using one architecture to build programs for another
225architecture. This can be as simple as using an Athlon (i686) to build a
226program for a K6-2 (i586), or using a Sparc to build a program for a ppc.
227</p>
228
229</body>
230</section>
231<section>
232<title>A Personal Note on Cross-compiling</title>
233<body>
234
235<p>
236I'd love to be able to help out on the Gentoo Cross-compiling effort, but I
237don't have any non-x86 machines. I can create things that work <e>in
238theory</e>, but I have to rely on other people to test what I write.
239That works to an extent, but it's tough. ;-)
240</p>
241
242<p>
243In the near future I hope to acquire a Sparc of some type to put Gentoo on so
244I can play around in-house.
245</p>
246
247</body>
248</section>
249</chapter>
250
251<chapter id="bootstrapping">
252<title>Using Distcc to Bootstrap</title>
253<section>
254<title>Step 1: Configure Portage </title>
255<body>
256
257<p>
258Boot your new box with a Gentoo Linux LiveCD and follow the <uri
259link="/doc/en/handbook/handbook-x86.xml?part=1">installation instructions</uri>
260up until the bootstrapping part. Then configure Portage to use distcc:
261</p>
262
263<pre caption="Preliminary Setup">
76# <i>nano -w /etc/make.conf</i> 264# <i>nano -w /etc/make.conf</i>
265<comment>(Add distcc to the FEATURES variable)</comment>
266FEATURES="distcc"
267<comment>(Set distcc's directory for temporary space)</comment>
268DISTCC_DIR="${PORTAGE_TMPDIR}/.distcc"
269<comment>(Modify MAKEOPTS to include -jN with N an appropriate integer)</comment>
77MAKE_OPTS=-jN 270MAKEOPTS="-jN"
78 </pre> 271</pre>
272
79 </body> 273</body>
80 </section> 274</section>
81 <section> 275<section>
82 <title>Setting up Distcc to Work With Automake</title> 276<title>Step 2: Getting Distcc</title>
83 <body> 277<body>
84 <p>This is in some cases easier than the Portage setup. What you have to do is update your <c>PATH</c> envvar to include <path>/usr/lib/distcc/bin</path> before where gcc (<path>/usr/bin</path>). However, there is a caveat. If you use ccache you have to put distcc after the ccache part. Like so:</p> 278
85 <pre caption="Setting your path"> 279<p>Before the installation of distcc, a user called distcc must be added to the
86# <i>export PATH="/usr/lib/ccache/bin:/usr/lib/distcc/bin:${PATH}"</i> 280<path>/etc/passwd</path>:</p>
281
282<pre caption="Create user distcc">
283# <i>echo "distcc:x:240:2:distccd:/dev/null:/bin/false" &gt;&gt; /etc/passwd</i>
87 </pre> 284</pre>
88 <p>Then, as you would normally type <c>make</c>, you would type <c>make -jN</c> (where N is an integer). A safe number to use for N varries on your network and the types of computers you are using to compile. For me, I have a dual processor P3 and a K6-2/400 that compile everything for my desktop (a 1200MHz Athlon Thunderbird) and I use -j5. Test your own settings to find the right number.</p> 285
286<p>
287Install distcc:
288</p>
289
290<pre caption="Getting Distcc on the new box">
291# <i>USE='-*' emerge --nodeps distcc</i>
292</pre>
293
89 </body> 294</body>
90 </section> 295</section>
91</chapter>
92
93<chapter>
94 <title>Cross-Compiling</title>
95 <section> 296<section>
96 <title>A Note on Cross-Compiling</title>
97 <body>
98 <p>Cross-compiling is using one architecture to build programs for another architecture. This can be as simple as using an Athlon (i686) to build a program for a K6-2 (i586), or using a Sparc to build a program for a ppc.</p>
99 </body>
100 </section>
101 <section>
102 <title>A Personal Note on Cross-compiling</title>
103 <body>
104 <p>I'd love to be able to help out on the Gentoo Cross-compiling effort, but I don't have any non-x86 machines. I can create things that work <e>in theory</e>, but I have to rely on other people to test what I write. That works to an extent, but it's tough. ;-)</p>
105 <p>In the near future I hope to acquire a Sparc of some type to put Gentoo on so I can play around in-house.</p>
106 </body>
107 </section>
108</chapter>
109
110<chapter>
111 <title>Known Problems With Distcc</title>
112 <section>
113 <title>Portage Doesn't Work With Distcc</title>
114 <body>
115 <p>This heading is a misnomer, really. The only thing that doens't work is the monitoring programs (<c>distccmon-text</c> and <c>distccmon-gnome</c>) with the standard distcc source. The reason for this is that distcc relies on the <c>TMPDIR</c> envvar, but Portage reassigns that.</p>
116 <p>The solution to this is a patch that changes the dependancy to <c>DISTCC_TMPDIR</c>. The patch is automatically applied to distcc. If you don't want to use <path>/tmp</path> (the default) you can reassign <c>DISTCC_TMPDIR</c>.</p>
117 <p>You may also notice that Distcc does not work with some packages. This can be a result of several things, such as an error in the .ebuild (Using <c>make</c> instead of <c>emake</c>) or an error in the program's Makefile, which the next section addresses.</p>
118 </body>
119 </section>
120 <section>
121 <title>Mozilla and Xfree</title>
122 <body>
123 <p>As you emerge various packages, you'll notice that they aren't being distributed (and indeed aren't being built in parallel). This is because the developers of Mozilla and Xfree .ebuilds disabled parallel building because it is known to cause problems. This isn't necessarily a distcc problem.</p>
124 <p>That isn't to say that sometimes distcc will cause a package to fail to compile.</p>
125 </body>
126 </section>
127</chapter>
128
129<chapter>
130 <title>Using Distcc to Bootstrap</title>
131 <section>
132 <title>Step 1: Build the Tarball</title>
133 <body>
134 <p>This section is helpful if you want to use Distcc during the Gentoo installation. Surprisingly it isn't that hard. What you'll need is another computer running Gentoo and a way to transfer a tarball to your new system (I use scp).</p>
135 <p>First you have to build a tarball of Distcc and include a library (<c>/usr/lib/libpopt.so.*</c>).</p>
136 <pre caption="Building the tarball">
137<i># USE='-gtk -selinux' emerge --buildpkg distcc
138# mkdir -p /tmp/distcc/usr/lib
139# cp /usr/portage/packages/sys-devel/distcc-DISTCC_VERSION.tbz2 /tmp/distcc/
140# cp /usr/lib/libpopt.so.* /tmp/distcc/usr/lib
141# cd /tmp/distcc
142# tar cfzv distcc.tar.gz *</i>
143<codenote>Be sure you replace DISTCC_VERSION with the version (and Gentoo revision) of Distcc, <c>like 2.10-r1</c></codenote>
144 </pre>
145 </body>
146 </section>
147 <section>
148 <title>Step 2: Setup on New Box</title>
149 <body>
150 <impo>Do not forget to start sshd and reset the root password for the LiveCD!</impo>
151 <p>Next, you have to boot your new box with a Gentoo Linux LiveCD and follow all of the steps up until the bootstrapping. Then procede with a little preliminary setup on the new box.</p>
152 <pre caption="Preliminary Setup">
153<codenote>Here we add distcc to FEATURES</codenote>
154<i># echo "FEATURES=\"\${FEATURES} distcc\"" >> /etc/make.conf</i>
155<codenote>You can also use <c>nano</c> to edit <c>/etc/make.conf</c> and manually add distcc to FEATURES.</codenote>
156<i># echo "MAKEOPTS=\"\${MAKEOPTS} -jN\"" >> /etc/make.conf</i>
157<codenote>Just like above, you can use <c>nano</c> to edit <c>/etc/make.conf</c> and manually change MAKEOPTS.</codenote>
158 </pre>
159 <p>Then add the distcc user to your <c>/etc/passwd</c>:</p>
160 <pre caption="Add the distcc user to /etc/passwd">
161<i># echo "distcc:x:240:2:distccd:/dev/null:/bin/false" >>/etc/passwd</i>
162<codenote>Do not forget the `<c>&gt;&gt;</c>'</codenote>
163 </pre>
164 </body>
165 </section>
166 <section>
167 <title>Step 3: Copy the Tarball</title>
168 <body>
169 <p>Next you will want to copy the distcc tarball that you made.</p>
170 <pre caption="Copy the tarball to the new box">
171<codenote>Execute this on the "old" box</codenote>
172<i># scp /tmp/distcc/distcc.tar.gz root@ip.of.new.box:/mnt/gentoo/</i>
173<codenote>Substitute <c>ip.of.new.box</c> for your new box's IP</codenote>
174 </pre>
175 </body>
176 </section>
177
178 <section>
179 <title>Step 4: Unpacking the Tarball</title>
180 <body>
181 <pre caption="Unpack the tarball">
182<i># tar xvfz distcc.tar.gz
183# tar xvfjp distcc-DISTCC_VERSION.tbz2</i>
184<codenote>Be sure you replace DISTCC_VERSION with the version (and Gentoo revision) of Distcc, <c>like 2.10-r1</c></codenote>
185 </pre>
186 </body>
187 </section>
188
189 <section>
190 <title>Step 5: Setting Up Distcc Itself</title> 297<title>Step 3: Setting Up Distcc</title>
191 <body> 298<body>
192 <p>Now set up distcc itself...</p> 299
300<p>
301Run <c>distcc-config</c> to setup distcc:
302</p>
303
193 <pre caption="Final distcc setup"> 304<pre caption="Final distcc setup">
194<i># /usr/bin/distcc-config --install 305<comment>(Substitute host1, host2, ... with the IP number(s) of the participating hosts)</comment>
195# /usr/bin/distcc-config --set-hosts "localhost host1 host2 host3 ..."</i> 306# <i>/usr/bin/distcc-config --set-hosts "localhost host1 host2 host3 ..."</i>
196 </pre> 307</pre>
197 308
198 <p>distcc should be set up now to bootstrap! Continue the official install guide, and dont forget to re-emerge distcc after <c>emerge system</c>.</p> 309<p>
310distcc is now set up to bootstrap! Continue the official installation
311instructions and <e>don't forget</e> to re-emerge distcc after <c>emerge
312system</c>. This is to make sure that all of the dependencies you want are
313installed as well.
314</p>
315
316<note>
317During bootstrap and <c>emerge system</c> Distcc may not appear to be used.
318This is expected as some ebuilds do not work well with distcc, so they
319intentionally disable it.
320</note>
321
199 </body> 322</body>
200 </section> 323</section>
201</chapter>
202
203
204<chapter> 324</chapter>
325
326<chapter>
327<title>Troubleshooting</title>
328<section>
329<title>Mozilla and Xfree</title>
330<body>
331
332<p>
333As you emerge various packages, you'll notice that some of them aren't being
334distributed (and aren't being built in parallel). This is because the
335developers of the Mozilla and Xfree ebuilds intentionally disable parallel
336building because it is known to cause problems.
337</p>
338
339<p>
340Sometimes distcc might cause a package to fail to compile. If this happens
341for you, please <uri link="http://bugs.gentoo.org">report</uri> it to us.
342</p>
343
344</body>
345</section>
346<section>
347<title>A Mixture of hardened-gcc and non-hardened-gcc Hosts Will Be Faulty</title>
348<body>
349
350<p>
351With such a long title any explanation here is almost irrelevent. However, if
352you plan to use distcc across hosts that have the <uri
353link="/proj/en/hardened/etdyn-ssp.xml">PaX/hardened-gcc</uri> and some that do
354not, you will run into problems.
355</p>
356
357<p>
358The solution requires a little foresight on your part; you have to run
359<c>hardened-gcc -R</c> on the host that has PaX/hardened-gcc, or you have to
360enable PaX protections in your kernel and <c>emerge hardened-gcc</c>. Both of
361which are a good thing to do since for the most part the protections offered
362by both packages is a good thing and is transparent to the user.
363</p>
364
365</body>
366</section>
367<section>
368<title>Mixed GCC Versions</title>
369<body>
370
371<p>
372If you have different GCC versions on your hosts, there will likely be very
373weird problems. The solution is to make certain all hosts have the same GCC
374version.
375</p>
376
377</body>
378</section>
379</chapter>
380
381<chapter>
205 <title>Distcc Extras</title> 382<title>Distcc Extras</title>
206 <section> 383<section>
207 <title>Distcc Monitors</title> 384<title>Distcc Monitors</title>
208 <body> 385<body>
209 <p>Distcc ships with two monitors. The text-based one is always built, it is called <c>distccmon-text</c>. Running it for the first time can be a bit confusing, but it is really quite easy to use. If you run the program with no parameter it will run once. However, if you pass it a number it will update every N seconds, where N is the argument you passed.</p> 386
210 <p>The other monitor is only turned on if you enabled <c>gtk</c> in your <c>USE</c> flags. This one is GTK+ based and runs in an X environment, and it is quite lovely.</p> 387<p>
211 <p>There is a caveat to using these programs. If you want to monitor any emerge, you have to start the monitor like so:</p> 388Distcc ships with two monitors. The text-based one is always built and is
389called <c>distccmon-text</c>. Running it for the first time can be a bit
390confusing, but it is really quite easy to use. If you run the program with no
391parameter it will run once. However, if you pass it a number it will update
392every N seconds, where N is the argument you passed.
393</p>
394
395<p>
396The other monitor is only turned on if you enabled <c>gtk</c> or <c>gnome</c>
397in your <c>USE</c> flags. This one is GTK+ based, runs in an X environment
398and it is quite lovely.
399</p>
400
212 <pre caption="Starting the monitors"> 401<pre caption="Starting the monitors">
213<i>sudo -u portage distccmon-text N</i> 402# <i>distccmon-text N</i>
214<codenote>Or you can start the graphical monitor...</codenote> 403<comment>(Or ...)</comment>
215<i>sudo -u portage distccmon-gnome</i> 404# <i>distccmon-gnome</i>
216<note>If you aren't using <c>userpriv</c> in your FEATURES, you should not use the '-u portage' part.</note>
217 </pre> 405</pre>
406
218 </body> 407</body>
219 </section> 408</section>
220</chapter>
221
222<chapter> 409</chapter>
410
411<chapter>
223 <title>Future Plans for Distcc and Gentoo</title> 412<title>Future Plans for Distcc and Gentoo</title>
224 <section> 413<section>
225 <title>distcc-subnetscan</title> 414<title>distcc-subnetscan</title>
226 <body> 415<body>
227 <p><c>distcc-subnetscan</c> is a perl program in development that will scan a subnet for hosts that have a participating distcc daemon. Even this will be enhanced to test if the daemon on a remote host will conform to a specific <c>CHOST</c> setting to make cross-compiling easier.</p> 416
417<p>
418<c>distcc-subnetscan</c> is a perl program in development that will scan a
419subnet for hosts that have a participating distcc daemon. Even this will be
420enhanced to test if the daemon on a remote host will conform to a specific
421<c>CHOST</c> setting to make cross-compiling easier.
422</p>
423
424<p>
228 <p>The perl script is being kept at <uri link="http://dev.gentoo.org/~lisa/distcc/distcc-subnetscan/distcc-subnetscan.pl">right here</uri> until a more formal home can be found.</p> 425The perl script is being kept at <uri link="http://dev.gentoo.org/~lisa/proj/distcc/distcc-subnetscan/distcc-subnetscan.html">lisa's
426dev page</uri> until a more formal home can be found.
427</p>
428
229 </body> 429</body>
230 </section> 430</section>
231 <section>
232 <title>distcc-config</title>
233 <body>
234 <p><c>distcc-config</c>, the userland configuration tool for distcc is out of date. Soon it will be rewritten to be brought up the current version of distcc.</p>
235 </body>
236 </section>
237</chapter> 431</chapter>
238
239</guide> 432</guide>

Legend:
Removed from v.1.3  
changed lines
  Added in v.1.21

  ViewVC Help
Powered by ViewVC 1.1.20