/[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.29 Revision 1.39
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.29 2005/07/02 04:50:55 smithj Exp $ --> 3<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/distcc.xml,v 1.39 2006/12/24 17:54:01 nightmorph Exp $ -->
4 4
5<guide link="/doc/en/distcc.xml"> 5<guide link="/doc/en/distcc.xml">
6 6
7<title>Gentoo Distcc Documentation</title> 7<title>Gentoo Distcc Documentation</title>
8 8
9<author title="Author"> 9<author title="Author">
10 <mail link="lisa@gentoo.org">Lisa Seelye</mail> 10 <mail link="lisa@gentoo.org">Lisa Seelye</mail>
11</author> 11</author>
12
13<author title="Editor"> 12<author title="Editor">
14 <mail link="vapier@gentoo.org">Mike Frysinger</mail> 13 <mail link="vapier@gentoo.org">Mike Frysinger</mail>
15</author> 14</author>
16
17<author title="Editor"> 15<author title="Editor">
18 <mail link="erwin@gentoo.org">Erwin</mail> 16 <mail link="erwin@gentoo.org">Erwin</mail>
19</author> 17</author>
20
21<author title="Editor"> 18<author title="Editor">
22 <mail link="swift@gentoo.org">Sven Vermeulen</mail> 19 <mail link="swift@gentoo.org">Sven Vermeulen</mail>
23</author> 20</author>
24
25<author title="Editor"> 21<author title="Editor">
26 <mail link="pylon@gentoo.org">Lars Weiler</mail> 22 <mail link="pylon@gentoo.org">Lars Weiler</mail>
27</author> 23</author>
28
29<author title="Reviewer"> 24<author title="Reviewer">
30 <mail link="blubber@gentoo.org">Tiemo Kieft</mail> 25 <mail link="blubber@gentoo.org">Tiemo Kieft</mail>
31</author> 26</author>
32 27
33<abstract> 28<abstract>
34This document serves as a HOWTO for using distcc with Gentoo. 29This document serves as a HOWTO for using distcc with Gentoo.
35</abstract> 30</abstract>
36 31
37<!-- 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 -->
38<!-- See http://creativecommons.org/licenses/by-sa/1.0 --> 33<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
39<license/> 34<license/>
40 35
41<version>1.12</version> 36<version>1.18</version>
42<date>2005-07-01</date> 37<date>2006-12-24</date>
43 38
44<chapter> 39<chapter>
45<title>Introduction</title> 40<title>Introduction</title>
46<section> 41<section>
47<title>What is distcc?</title> 42<title>What is distcc?</title>
103</p> 98</p>
104 99
105<pre caption="Installing distcc"> 100<pre caption="Installing distcc">
106# <i>emerge distcc</i> 101# <i>emerge distcc</i>
107</pre> 102</pre>
103
104<impo>
105Remember, you must be sure to install distcc on all of your participating
106machines.
107</impo>
108 108
109</body> 109</body>
110</section> 110</section>
111<section> 111<section>
112<title>Setting up Portage to use Distcc</title> 112<title>Setting up Portage to use Distcc</title>
181link="http://distcc.samba.org/security.html">Distcc Security Design</uri>. 181link="http://distcc.samba.org/security.html">Distcc Security Design</uri>.
182</p> 182</p>
183 183
184<impo> 184<impo>
185It is important to use --allow and --listen. Please read the distccd manpage 185It is important to use --allow and --listen. Please read the distccd manpage
186or the above seurity document for more information. 186or the above security document for more information.
187</impo> 187</impo>
188 188
189 189
190<p> 190<p>
191Now start the distcc daemon on all the participating computers: 191Now start the distcc daemon on all the participating computers:
212the ccache part: 212the ccache part:
213</p> 213</p>
214 214
215<pre caption="Setting your path"> 215<pre caption="Setting your path">
216# <i>export PATH="/usr/lib/ccache/bin:/usr/lib/distcc/bin:${PATH}"</i> 216# <i>export PATH="/usr/lib/ccache/bin:/usr/lib/distcc/bin:${PATH}"</i>
217<comment>You can put this in your .bashrc or equivelant file to have the PATH 217<comment>(You can put this in your ~/.bashrc or equivalent file to have the PATH
218set every time you log in</comment> 218set every time you log in)</comment>
219</pre> 219</pre>
220 220
221<p> 221<p>
222Then, as you would normally type <c>make</c>, you would type <c>make -jN</c> 222Then, as you would normally type <c>make</c>, you would type <c>make -jN</c>
223(where N is an integer). The value of N depends on your network and the types 223(where N is an integer). The value of N depends on your network and the types
230</chapter> 230</chapter>
231 231
232<chapter> 232<chapter>
233<title>Cross-Compiling</title> 233<title>Cross-Compiling</title>
234<section> 234<section>
235<title>A Note on Cross-Compiling</title>
236<body> 235<body>
237 236
238<p> 237<p>
239Cross-compiling is using one architecture to build programs for another 238Cross-compiling is using one architecture to build programs for another
240architecture. This can be as simple as using an Athlon (i686) to build a 239architecture. This can be as simple as using an Athlon (i686) to build a
241program for a K6-2 (i586), or using a Sparc to build a program for a ppc. 240program for a K6-2 (i586), or using a Sparc to build a program for a ppc. This
242</p> 241is documented in our <uri link="/doc/en/cross-compiling-distcc.xml">DistCC
243 242Cross-compiling Guide</uri>.
244</body>
245</section>
246<section>
247<title>An Introduction to Cross-Compiling</title>
248<body>
249
250<p>
251If you want to give cross-compiling a try you can to follow <uri
252link="http://dev.gentoo.org/~vapier/CROSS-COMPILE-HOWTO">The Cross Compile
253HOWTO</uri>; Crossdev is deprecated.
254</p> 243</p>
255 244
256</body> 245</body>
257</section> 246</section>
258</chapter> 247</chapter>
260<chapter id="bootstrapping"> 249<chapter id="bootstrapping">
261<title>Using Distcc to Bootstrap</title> 250<title>Using Distcc to Bootstrap</title>
262<section> 251<section>
263<title>Step 1: Configure Portage</title> 252<title>Step 1: Configure Portage</title>
264<body> 253<body>
265 254<!--
255Note that this will need to become a link to the old 2005.1 networked handbooks
256once the 2006.0 handbooks are released. Until then, the link can stay.
257-->
266<p> 258<p>
267Boot your new box with a Gentoo Linux LiveCD and follow the <uri 259Boot your new box with a Gentoo Linux LiveCD and follow the <uri
268link="/doc/en/handbook/handbook-x86.xml?part=1">installation instructions</uri> 260link="/doc/en/handbook/handbook-x86.xml?part=1">installation instructions</uri>
261up until the bootstrapping part. (See the <uri
262link="/doc/en/faq.xml#stage12">Gentoo FAQ</uri> for more information about
269up until the bootstrapping part. Then configure Portage to use distcc: 263bootstrapping.) Then configure Portage to use distcc:
270</p> 264</p>
271 265
272<pre caption="Preliminary Setup"> 266<pre caption="Preliminary Setup">
273# <i>nano -w /etc/make.conf</i> 267# <i>nano -w /etc/make.conf</i>
274<comment>(Add distcc to the FEATURES</comment> 268<comment>(Add distcc to the FEATURES</comment>
325<comment>(Substitute host1, host2, ... with the IP number(s) of the 319<comment>(Substitute host1, host2, ... with the IP number(s) of the
326participating hosts)</comment> 320participating hosts)</comment>
327# <i>/usr/bin/distcc-config --set-hosts "localhost host1 host2 host3 ..."</i> 321# <i>/usr/bin/distcc-config --set-hosts "localhost host1 host2 host3 ..."</i>
328<comment>An example: <i>/usr/bin/distcc-config --set-hosts "localhost 322<comment>An example: <i>/usr/bin/distcc-config --set-hosts "localhost
329192.168.0.4 192.168.0.6"</i></comment> 323192.168.0.4 192.168.0.6"</i></comment>
330</pre> 324</pre>
331 325
332<p> 326<p>
333Distcc is now set up to bootstrap! Continue with the official installation 327Distcc is now set up to bootstrap! Continue with the official installation
334instructions and <e>do not forget</e> to re-emerge distcc after <c>emerge 328instructions and <e>do not forget</e> to re-emerge distcc after <c>emerge
335system</c>. This is to make sure that all of the dependencies you want are 329system</c>. This is to make sure that all of the dependencies you want are
347</chapter> 341</chapter>
348 342
349<chapter> 343<chapter>
350<title>Troubleshooting</title> 344<title>Troubleshooting</title>
351<section> 345<section>
352<title>Mozilla and Xfree</title> 346<title>Some Packages Don't Use Distcc</title>
353<body> 347<body>
354 348
355<p> 349<p>
356As you emerge various packages, you'll notice that some of them aren't being 350As you emerge various packages, you'll notice that some of them aren't being
357distributed (and aren't being built in parallel). This is because the 351distributed (and aren't being built in parallel). This may happen because the
358developers of the Mozilla and Xfree ebuilds intentionally disable parallel 352package's Makefile doesn't support parallel operations or the maintainer of the
359building because it is known to cause problems. 353ebuild has explicitly disabled parallel operations due to a known problem.
360</p> 354</p>
361 355
362<p> 356<p>
363Sometimes distcc might cause a package to fail to compile. If this happens 357Sometimes distcc might cause a package to fail to compile. If this happens
364for you, please <uri link="http://bugs.gentoo.org">report</uri> it to us. 358for you, please <uri link="http://bugs.gentoo.org">report</uri> it to us.
365</p>
366
367</body>
368</section>
369<section>
370<title>A Mixture of hardened-gcc and non-hardened-gcc Hosts Will Be Faulty</title>
371<body>
372
373<p>
374With such a long title any explanation here is almost irrelevent. However, if
375you plan to use distcc across hosts that have the <uri
376link="/proj/en/hardened/etdyn-ssp.xml">PaX/hardened-gcc</uri> and some that do
377not, you will run into problems.
378</p>
379
380<p>
381The solution requires a little foresight on your part; you have to run
382<c>hardened-gcc -R</c> on the host that has PaX/hardened-gcc, or you have to
383enable PaX protections in your kernel and <c>emerge hardened-gcc</c>. Both of
384which are a good thing to do since for the most part the protections offered
385by both packages is a good thing and is transparent to the user.
386</p> 359</p>
387 360
388</body> 361</body>
389</section> 362</section>
390<section> 363<section>

Legend:
Removed from v.1.29  
changed lines
  Added in v.1.39

  ViewVC Help
Powered by ViewVC 1.1.20