| 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.32 2006/01/25 09:16:29 neysx Exp $ --> |
3 | <!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/distcc.xml,v 1.33 2006/02/18 23:21:44 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 | |
| … | |
… | |
| 31 | |
31 | |
| 32 | <!-- 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 --> |
| 33 | <!-- See http://creativecommons.org/licenses/by-sa/1.0 --> |
33 | <!-- See http://creativecommons.org/licenses/by-sa/1.0 --> |
| 34 | <license/> |
34 | <license/> |
| 35 | |
35 | |
| 36 | <version>1.13</version> |
36 | <version>1.14</version> |
| 37 | <date>2006-01-25</date> |
37 | <date>2006-02-18</date> |
| 38 | |
38 | |
| 39 | <chapter> |
39 | <chapter> |
| 40 | <title>Introduction</title> |
40 | <title>Introduction</title> |
| 41 | <section> |
41 | <section> |
| 42 | <title>What is distcc?</title> |
42 | <title>What is distcc?</title> |
| … | |
… | |
| 244 | <chapter id="bootstrapping"> |
244 | <chapter id="bootstrapping"> |
| 245 | <title>Using Distcc to Bootstrap</title> |
245 | <title>Using Distcc to Bootstrap</title> |
| 246 | <section> |
246 | <section> |
| 247 | <title>Step 1: Configure Portage</title> |
247 | <title>Step 1: Configure Portage</title> |
| 248 | <body> |
248 | <body> |
| 249 | |
249 | <!-- |
|
|
250 | Note that this will need to become a link to the old 2005.1 networked handbooks |
|
|
251 | once the 2006.0 handbooks are released. Until then, the link can stay. |
|
|
252 | --> |
| 250 | <p> |
253 | <p> |
| 251 | Boot your new box with a Gentoo Linux LiveCD and follow the <uri |
254 | Boot your new box with a Gentoo Linux LiveCD and follow the <uri |
| 252 | link="/doc/en/handbook/handbook-x86.xml?part=1">installation instructions</uri> |
255 | link="/doc/en/handbook/handbook-x86.xml?part=1">installation instructions</uri> |
|
|
256 | up until the bootstrapping part. (See the <uri |
|
|
257 | link="http://www.gentoo.org/doc/en/faq.xml#stage12">Gentoo FAQ</uri> for more |
| 253 | up until the bootstrapping part. Then configure Portage to use distcc: |
258 | information about bootstrapping.) Then configure Portage to use distcc: |
| 254 | </p> |
259 | </p> |
| 255 | |
260 | |
| 256 | <pre caption="Preliminary Setup"> |
261 | <pre caption="Preliminary Setup"> |
| 257 | # <i>nano -w /etc/make.conf</i> |
262 | # <i>nano -w /etc/make.conf</i> |
| 258 | <comment>(Add distcc to the FEATURES</comment> |
263 | <comment>(Add distcc to the FEATURES</comment> |
| … | |
… | |
| 331 | </chapter> |
336 | </chapter> |
| 332 | |
337 | |
| 333 | <chapter> |
338 | <chapter> |
| 334 | <title>Troubleshooting</title> |
339 | <title>Troubleshooting</title> |
| 335 | <section> |
340 | <section> |
| 336 | <title>Mozilla and Xfree</title> |
341 | <title>Mozilla and Xorg</title> |
| 337 | <body> |
342 | <body> |
| 338 | |
343 | |
| 339 | <p> |
344 | <p> |
| 340 | As you emerge various packages, you'll notice that some of them aren't being |
345 | As you emerge various packages, you'll notice that some of them aren't being |
| 341 | distributed (and aren't being built in parallel). This is because the |
346 | distributed (and aren't being built in parallel). This is because the |
| 342 | developers of the Mozilla and Xfree ebuilds intentionally disable parallel |
347 | developers of the Mozilla and Xorg-X11 ebuilds intentionally disable parallel |
| 343 | building because it is known to cause problems. |
348 | building because it is known to cause problems. |
| 344 | </p> |
349 | </p> |
| 345 | |
350 | |
| 346 | <p> |
351 | <p> |
| 347 | Sometimes distcc might cause a package to fail to compile. If this happens |
352 | Sometimes distcc might cause a package to fail to compile. If this happens |
| 348 | for you, please <uri link="http://bugs.gentoo.org">report</uri> it to us. |
353 | for you, please <uri link="http://bugs.gentoo.org">report</uri> it to us. |
| 349 | </p> |
|
|
| 350 | |
|
|
| 351 | </body> |
|
|
| 352 | </section> |
|
|
| 353 | <section> |
|
|
| 354 | <title>A Mixture of hardened-gcc and non-hardened-gcc Hosts Will Be Faulty</title> |
|
|
| 355 | <body> |
|
|
| 356 | |
|
|
| 357 | <p> |
|
|
| 358 | With such a long title any explanation here is almost irrelevent. However, if |
|
|
| 359 | you plan to use distcc across hosts that have the <uri |
|
|
| 360 | link="/proj/en/hardened/etdyn-ssp.xml">PaX/hardened-gcc</uri> and some that do |
|
|
| 361 | not, you will run into problems. |
|
|
| 362 | </p> |
|
|
| 363 | |
|
|
| 364 | <p> |
|
|
| 365 | The solution requires a little foresight on your part; you have to run |
|
|
| 366 | <c>hardened-gcc -R</c> on the host that has PaX/hardened-gcc, or you have to |
|
|
| 367 | enable PaX protections in your kernel and <c>emerge hardened-gcc</c>. Both of |
|
|
| 368 | which are a good thing to do since for the most part the protections offered |
|
|
| 369 | by both packages is a good thing and is transparent to the user. |
|
|
| 370 | </p> |
354 | </p> |
| 371 | |
355 | |
| 372 | </body> |
356 | </body> |
| 373 | </section> |
357 | </section> |
| 374 | <section> |
358 | <section> |
Parent Directory
| 
Revision Log
| 
Patch