/[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.20 Revision 1.40
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.20 2004/07/11 13:13:49 pylon Exp $ --> 3<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/distcc.xml,v 1.40 2007/06/21 23:46:16 rane Exp $ -->
4
5<!--
6 Synchronised with rev 1.15 on
7 http://www.thedoh.com/viewcvs/distcc/html/distcc.xml
8-->
9 4
10<guide link="/doc/en/distcc.xml"> 5<guide link="/doc/en/distcc.xml">
11 6
12<title>Gentoo Distcc Documentation</title> 7<title>Gentoo Distcc Documentation</title>
13 8
14<author title="Author"> 9<author title="Author">
15 <mail link="lisa@gentoo.org">Lisa Seelye</mail> 10 <mail link="lisa@gentoo.org">Lisa Seelye</mail>
16</author> 11</author>
17
18<author title="Editor"> 12<author title="Editor">
19 <mail link="vapier@gentoo.org">Mike Frysinger</mail> 13 <mail link="vapier@gentoo.org">Mike Frysinger</mail>
20</author> 14</author>
21
22<author title="Editor"> 15<author title="Editor">
23 <mail link="erwin@gentoo.org">Erwin</mail> 16 <mail link="erwin@gentoo.org">Erwin</mail>
24</author> 17</author>
25
26<author title="Editor"> 18<author title="Editor">
27 <mail link="swift@gentoo.org">Sven Vermeulen</mail> 19 <mail link="swift@gentoo.org">Sven Vermeulen</mail>
28</author> 20</author>
29
30<author title="Editor"> 21<author title="Editor">
31 <mail link="pylon@gentoo.org">Lars Weiler</mail> 22 <mail link="pylon@gentoo.org">Lars Weiler</mail>
32</author> 23</author>
33
34<author title="Reviewer"> 24<author title="Reviewer">
35 <mail link="blubber@gentoo.org">Tiemo Kieft</mail> 25 <mail link="blubber@gentoo.org">Tiemo Kieft</mail>
36</author> 26</author>
37 27
38<abstract> 28<abstract>
39This document serves as a HOWTO for using distcc with Gentoo. 29This document serves as a HOWTO for using distcc with Gentoo.
40</abstract> 30</abstract>
41 31
42<!-- The content of this document is licensed under the CC-BY-SA license --> 32<!-- The content of this document is licensed under the CC-BY-SA license -->
43<!-- See http://creativecommons.org/licenses/by-sa/1.0 --> 33<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
44<license/> 34<license/>
45 35
46<version>1.7.1</version> 36<version>1.19</version>
47<date>July 11, 2004</date> 37<date>2007-06-22</date>
48 38
49<chapter> 39<chapter>
50<title>Introduction</title> 40<title>Introduction</title>
51<section> 41<section>
52<title>What is distcc?</title> 42<title>What is distcc?</title>
53<body> 43<body>
54 44
55<p> 45<p>
56Distcc is a program designed to distribute compiling tasks across a network to 46Distcc 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 47participating hosts. It is comprised of a server, <c>distccd</c>, and a client
58program, <c>distcc</c>. Distcc can work transparently with <uri 48program, <c>distcc</c>. Distcc can work transparently with <uri
59link="http://ccache.samba.org">ccache</uri> and Portage with a little work. 49link="http://ccache.samba.org">ccache</uri>, Portage, and Automake with a
50little setup.
60</p> 51</p>
61 52
62</body> 53</body>
63</section> 54</section>
64<section> 55<section>
65<title>Using distcc to bootstrap</title> 56<title>Using distcc to bootstrap</title>
66<body> 57<body>
67 58
68<p> 59<p>
69If you are planning on using distcc to help you bootstrap a Gentoo installation, 60If you are planning on using distcc to help you bootstrap a Gentoo
70make sure you read the part on <uri link="#bootstrapping">Using distcc to 61installation, make sure you read the section <uri link="#bootstrapping">Using
71Bootstrap</uri> which is situated further down in this document. 62distcc to Bootstrap</uri>, which is situated further down in this document.
72</p> 63</p>
73 64
74</body> 65</body>
75</section> 66</section>
76</chapter> 67</chapter>
80<section> 71<section>
81<title>Dependencies</title> 72<title>Dependencies</title>
82<body> 73<body>
83 74
84<p> 75<p>
85To start off with, to use Distcc all of the computers on your network need to 76In order to use Distcc, all of the computers on your network need to have the
86have the same GCC versions. Mixing 3.3.x (where the x varies) is okay, but 77same GCC versions. For example, 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. 78mixing 3.3.x with 3.2.x <b>may</b> result in compilation errors or runtime
79errors.
88</p> 80</p>
89 81
90</body> 82</body>
91</section> 83</section>
92<section> 84<section>
93<title>Installing Distcc</title> 85<title>Installing Distcc</title>
94<body> 86<body>
95 87
96<p> 88<p>
97There are a couple of options you should know about before you start 89There are a couple of options you should be aware of before you start
98installing distcc. 90installing distcc.
99</p> 91</p>
100 92
101<p> 93<p>
102Distcc ships with a graphical monitor to monitor tasks that your computer is 94Distcc ships with a graphical monitor to monitor tasks that your computer is
107 99
108<pre caption="Installing distcc"> 100<pre caption="Installing distcc">
109# <i>emerge distcc</i> 101# <i>emerge distcc</i>
110</pre> 102</pre>
111 103
104<impo>
105Remember, you must be sure to install distcc on all of your participating
106machines.
107</impo>
108
112</body> 109</body>
113</section> 110</section>
114<section> 111<section>
115<title>Setting up Portage to use Distcc</title> 112<title>Setting up Portage to use Distcc</title>
116<body> 113<body>
117 114
118<p> 115<p>
119Setting up distcc is easy to do with Portage. Execute the following steps on 116Setting up Portage to use distcc is easy. Execute the following steps on
120each system that should participate in the distributed compiling: 117each system that should participate in the distributed compiling:
121</p> 118</p>
122 119
123<pre caption="Integrating Distcc and Portage"> 120<pre caption="Integrating Distcc and Portage">
124# <i>emerge distcc</i> 121# <i>emerge distcc distcc-config</i>
125# <i>nano -w /etc/make.conf</i> 122# <i>nano -w /etc/make.conf</i>
126<comment>(Set N to a suitable number for your particular setup)</comment> 123<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> 124<comment>(A common strategy is setting N as twice the number of total CPUs + 1 available)</comment>
128MAKEOPTS="-jN" 125MAKEOPTS="-jN"
129<comment>(Add distcc to your FEATURES variable)</comment> 126<comment>(Add distcc to your FEATURES)</comment>
130FEATURES="distcc" 127FEATURES="distcc"
131</pre> 128</pre>
132 129
130</body>
131</section>
132<section>
133<title>Specifying Participating Hosts</title>
134<body>
135
133<p> 136<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 137Use the <c>distcc-config</c> command to set the list of hosts. Here is an
136some hosts that might be in your list: 138example of some hosts that might be in your list:
137</p> 139</p>
138 140
139<pre caption="Examples of host definitions"> 141<pre caption="Examples of host definitions">
140192.168.0.1 192.168.0.2 192.168.0.3 142192.168.0.1 192.168.0.2 192.168.0.3
141192.168.0.1/2 192.168.0.2 192.168.0.3/10 143192.168.0.1/2 192.168.0.2 192.168.0.3/10
142192.168.0.1:4000/2 192.168.0.2/1 192.168.0.3:3632/4 144192.168.0.1:4000/2 192.168.0.2/1 192.168.0.3:3632/4
143@192.168.0.1 @192.168.0.2:/usr/bin/distccd 192.168.0.3 145@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 146<comment>(There are also several other methods of setting up hosts. See the
145distcc manpage for more details.)</comment> 147distcc manpage for more details.)</comment>
148<comment>If you wish to compile on the local machine you should put 'localhost'
149in the hosts list. Conversely if you do not wish to use the local machine to
150compile (which is often the case) omit it from the hosts list. On a slow
151machine using localhost may actually slow things down. Make sure to test your
152settings for performance.</comment>
146</pre> 153</pre>
147 154
148<p> 155<p>
149It may all look complicated, but in most cases a variant of line 1 or 2 will 156It may all look complicated, but in most cases a variant of line 1 or 2 will
150work. 157work.
151</p> 158</p>
152 159
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> 160<p>
162Since most people won't be using lines 3 or 4, I'll <uri 161Since 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 162link="http://distcc.samba.org/man/distcc_1.html">refer to</uri> the distcc
164docs for more information. 163docs (man distcc) for more information.
165</p> 164</p>
166 165
167<p> 166<p>
168For instance, to set the first line in the previous example: 167For instance, to set the first line in the previous example:
169</p> 168</p>
170 169
171<pre caption="Sample command to set the hosts"> 170<pre caption="Sample command to set the hosts">
172# <i>/usr/bin/distcc-config --set-hosts "192.168.0.1 192.168.0.2 192.168.0.3"</i> 171# <i>/usr/bin/distcc-config --set-hosts "192.168.0.1 192.168.0.2 192.168.0.3"</i>
173</pre> 172</pre>
173
174<p>
175Edit <path>/etc/conf.d/distccd</path> to your needs and be sure to set the
176<c>--allow</c> directive to allow only hosts you trust. For added security,
177you should also use the <c>--listen</c> directive to tell the distcc daemon
178what IP to listen on (for multi-homed systems). More information on distcc
179security can be found at <uri
180link="http://distcc.samba.org/security.html">Distcc Security Design</uri>.
181</p>
182
183<impo>
184It is important to use --allow and --listen. Please read the distccd manpage
185or the above security document for more information.
186</impo>
187
174 188
175<p> 189<p>
176Now start the distcc daemon on all the participating computers: 190Now start the distcc daemon on all the participating computers:
177</p> 191</p>
178 192
188<section> 202<section>
189<title>Setting up Distcc to Work With Automake</title> 203<title>Setting up Distcc to Work With Automake</title>
190<body> 204<body>
191 205
192<p> 206<p>
193This is in some cases easier than the Portage setup. What you have to do is 207This 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> 208update 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>). 209in 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 210However, there is a caveat. If you use ccache you have to put distcc after
197the ccache part: 211the ccache part:
198</p> 212</p>
199 213
200<pre caption="Setting your path"> 214<pre caption="Setting your path">
201# <i>export PATH="/usr/lib/ccache/bin:/usr/lib/distcc/bin:${PATH}"</i> 215# <i>export PATH="/usr/lib/ccache/bin:/usr/lib/distcc/bin:${PATH}"</i>
216<comment>(You can put this in your ~/.bashrc or equivalent file to have the PATH
217set every time you log in)</comment>
202</pre> 218</pre>
203 219
204<p> 220<p>
205Then, as you would normally type <c>make</c>, you would type <c>make -jN</c> 221Then, 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 222(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 223of computers you are using to compile. Test your own settings to find the
208a K6-2/400 that compiles everything for my desktop (a 1200MHz Athlon 224number that yields the best performance.
209Thunderbird) and I use -j5. Test your own settings to find the most
210performant number.
211</p> 225</p>
212 226
213</body> 227</body>
214</section> 228</section>
215</chapter> 229</chapter>
216 230
217<chapter> 231<chapter>
218<title>Cross-Compiling</title> 232<title>Cross-Compiling</title>
219<section> 233<section>
220<title>A Note on Cross-Compiling</title>
221<body> 234<body>
222 235
223<p> 236<p>
224Cross-compiling is using one architecture to build programs for another 237Cross-compiling is using one architecture to build programs for another
225architecture. This can be as simple as using an Athlon (i686) to build a 238architecture. 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. 239program for a K6-2 (i586), or using a Sparc to build a program for a ppc. This
227</p> 240is documented in our <uri link="/doc/en/cross-compiling-distcc.xml">DistCC
228 241Cross-compiling Guide</uri>.
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> 242</p>
246 243
247</body> 244</body>
248</section> 245</section>
249</chapter> 246</chapter>
250 247
251<chapter id="bootstrapping"> 248<chapter id="bootstrapping">
252<title>Using Distcc to Bootstrap</title> 249<title>Using Distcc to Bootstrap</title>
253<section> 250<section>
254<title>Step 1: Configure Portage </title> 251<title>Step 1: Configure Portage</title>
255<body> 252<body>
256 253<!--
254Note that this will need to become a link to the old 2005.1 networked handbooks
255once the 2006.0 handbooks are released. Until then, the link can stay.
256-->
257<p> 257<p>
258Boot your new box with a Gentoo Linux LiveCD and follow the <uri 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> 259link="/doc/en/handbook/handbook-x86.xml?part=1">installation instructions</uri>
260up until the bootstrapping part. (See the <uri
261link="/doc/en/faq.xml#stage12">Gentoo FAQ</uri> for more information about
260up until the bootstrapping part. Then configure Portage to use distcc: 262bootstrapping.) Then configure Portage to use distcc:
261</p> 263</p>
262 264
263<pre caption="Preliminary Setup"> 265<pre caption="Preliminary Setup">
264# <i>nano -w /etc/make.conf</i> 266# <i>nano -w /etc/make.conf</i>
265<comment>(Add distcc to the FEATURES variable)</comment> 267<comment>(Add distcc to the FEATURES</comment>
266FEATURES="distcc" 268FEATURES="distcc"
267<comment>(Set distcc's directory for temporary space)</comment> 269<comment>(Modify MAKEOPTS to include -jN, where N is twice the number of CPUs
268DISTCC_DIR="${PORTAGE_TMPDIR}/.distcc" 270+1 available)</comment>
269<comment>(Modify MAKEOPTS to include -jN with N an appropriate integer)</comment>
270MAKEOPTS="-jN" 271MAKEOPTS="-jN"
271</pre> 272</pre>
272 273
274<pre caption="Setting your path">
275# <i>export PATH="/usr/lib/ccache/bin:/usr/lib/distcc/bin:${PATH}"</i>
276</pre>
277
273</body> 278</body>
274</section> 279</section>
275<section> 280<section>
276<title>Step 2: Getting Distcc</title> 281<title>Step 2: Getting Distcc</title>
277<body> 282<body>
278 283
279<p>Before the installation of distcc, a user called distcc must be added to the
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>
284</pre>
285
286<p> 284<p>
287Install distcc: 285Install distcc:
288</p> 286</p>
289 287
290<pre caption="Getting Distcc on the new box"> 288<pre caption="Getting Distcc on the new box">
291# <i>USE='-*' emerge --nodeps distcc</i> 289# <i>USE='-*' emerge --nodeps sys-devel/distcc sys-devel/distcc-config</i>
292</pre> 290</pre>
293 291
294</body> 292</body>
295</section> 293</section>
296<section> 294<section>
297<title>Step 3: Setting Up Distcc</title> 295<title>Step 3: Setting Up Distcc</title>
298<body> 296<body>
299 297
300<p> 298<p>
301Run <c>distcc-config</c> to setup distcc: 299Run <c>distcc-config --install</c> to setup distcc:
302</p> 300</p>
303 301
304<pre caption="Final distcc setup"> 302<pre caption="Final distcc setup">
305<comment>(Substitute host1, host2, ... with the IP number(s) of the participating hosts)</comment> 303<comment>(Substitute host1, host2, ... with the IP number(s) of the
304participating hosts)</comment>
306# <i>/usr/bin/distcc-config --set-hosts "localhost host1 host2 host3 ..."</i> 305# <i>/usr/bin/distcc-config --set-hosts "localhost host1 host2 host3 ..."</i>
306<comment>An example: <i>/usr/bin/distcc-config --set-hosts "localhost
307192.168.0.4 192.168.0.6"</i></comment>
307</pre> 308</pre>
308 309
309<p> 310<p>
310distcc is now set up to bootstrap! Continue the official installation 311Distcc is now set up to bootstrap! Continue with the official installation
311instructions and <e>don't forget</e> to re-emerge distcc after <c>emerge 312instructions and <e>do not forget</e> to re-emerge distcc after <c>emerge
312system</c>. This is to make sure that all of the dependencies you want are 313system</c>. This is to make sure that all of the dependencies you want are
313installed as well. 314installed as well.
314</p> 315</p>
315 316
316<note> 317<note>
317During bootstrap and <c>emerge system</c> Distcc may not appear to be used. 318During 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 319This is expected as some ebuilds do not work well with distcc, so they
319intentionally disable it. 320intentionally disable it.
320</note> 321</note>
321 322
322</body> 323</body>
324</chapter> 325</chapter>
325 326
326<chapter> 327<chapter>
327<title>Troubleshooting</title> 328<title>Troubleshooting</title>
328<section> 329<section>
329<title>Mozilla and Xfree</title> 330<title>Some Packages Don't Use Distcc</title>
330<body> 331<body>
331 332
332<p> 333<p>
333As you emerge various packages, you'll notice that some of them aren't being 334As 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 335distributed (and aren't being built in parallel). This may happen because the
335developers of the Mozilla and Xfree ebuilds intentionally disable parallel 336package's Makefile doesn't support parallel operations or the maintainer of the
336building because it is known to cause problems. 337ebuild has explicitly disabled parallel operations due to a known problem.
337</p> 338</p>
338 339
339<p> 340<p>
340Sometimes distcc might cause a package to fail to compile. If this happens 341Sometimes 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. 342for 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> 343</p>
364 344
365</body> 345</body>
366</section> 346</section>
367<section> 347<section>
371<p> 351<p>
372If you have different GCC versions on your hosts, there will likely be very 352If 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 353weird problems. The solution is to make certain all hosts have the same GCC
374version. 354version.
375</p> 355</p>
356
357<p>
358Recent Portage updates have made Portage use <c>${CHOST}-gcc</c> instead of
359<c>gcc</c>. This means that if you're mixing i686 machines with other types
360(i386, i586) you will run into problems. A workaround for this may be to
361<c>export CC='gcc' CXX='c++'</c> or to put it in <path>/etc/make.conf</path>.
362</p>
363
364<impo>
365Doing this explicitly redefines some behaviour of Portage and may have some
366weird results in the future. Only do this if you're mixing CHOSTs.
367</impo>
368
376 369
377</body> 370</body>
378</section> 371</section>
379</chapter> 372</chapter>
380 373
391parameter it will run once. However, if you pass it a number it will update 384parameter it will run once. However, if you pass it a number it will update
392every N seconds, where N is the argument you passed. 385every N seconds, where N is the argument you passed.
393</p> 386</p>
394 387
395<p> 388<p>
396The other monitor is only turned on if you enabled <c>gtk</c> or <c>gnome</c> 389The 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 390in your <c>USE</c> flags. This one is GTK+ based, runs in an X environment
398and it is quite lovely. 391and it is quite lovely. For Gentoo the GUI monitor has been called
392<c>distccmon-gui</c> for less confusion. Elsewhere it may be referred to as
393<c>distccmon-gnome</c>.
399</p> 394</p>
400 395
401<pre caption="Starting the monitors"> 396<pre caption="Starting the monitors">
402# <i>distccmon-text N</i> 397# <i>distccmon-text N</i>
403<comment>(Or ...)</comment> 398<comment>(Or)</comment>
404# <i>distccmon-gnome</i> 399# <i>distccmon-gui</i>
405</pre> 400<comment>To monitor Portage's distcc usage you can use:</comment>
406 401# <i>DISTCC_DIR="/var/tmp/portage/.distcc/" distccmon-text N</i>
407</body> 402<comment>(Or)</comment>
408</section> 403# <i>DISTCC_DIR="/var/tmp/portage/.distcc/" distccmon-gui</i>
409</chapter>
410
411<chapter>
412<title>Future Plans for Distcc and Gentoo</title>
413<section>
414<title>distcc-subnetscan</title>
415<body>
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> 404</pre>
423 405
424<p> 406<impo>
425The perl script is being kept at <uri link="http://dev.gentoo.org/~lisa/distcc/distcc-subnetscan/distcc-subnetscan.pl">lisa's 407If your distcc directory is elsewhere, change the DISTCC_DIR variable
426dev page</uri> until a more formal home can be found. 408accordingly.
427</p> 409</impo>
428 410
429</body> 411</body>
430</section> 412</section>
431</chapter> 413</chapter>
432</guide> 414</guide>

Legend:
Removed from v.1.20  
changed lines
  Added in v.1.40

  ViewVC Help
Powered by ViewVC 1.1.20