From: "Josh Saddler" <nightmorph@lark.gentoo.org>
To: gentoo-doc-cvs@lists.gentoo.org
Subject: [gentoo-doc-cvs] cvs commit: distcc.xml
Date: Sat, 18 Feb 2006 23:21:44 +0000 [thread overview]
Message-ID: <200602182321.k1INLjmP016840@robin.gentoo.org> (raw)
nightmorph 06/02/18 23:21:44
Modified: xml/htdocs/doc/en distcc.xml
Log:
updated distcc guide for bug 123231
Revision Changes Path
1.33 +17 -33 xml/htdocs/doc/en/distcc.xml
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/distcc.xml?rev=1.33&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/distcc.xml?rev=1.33&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/distcc.xml.diff?r1=1.32&r2=1.33&cvsroot=gentoo
Index: distcc.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/distcc.xml,v
retrieving revision 1.32
retrieving revision 1.33
diff -u -r1.32 -r1.33
--- distcc.xml 25 Jan 2006 09:16:29 -0000 1.32
+++ distcc.xml 18 Feb 2006 23:21:44 -0000 1.33
@@ -1,6 +1,6 @@
<?xml version='1.0' encoding="UTF-8"?>
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/distcc.xml,v 1.32 2006/01/25 09:16:29 neysx Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/distcc.xml,v 1.33 2006/02/18 23:21:44 nightmorph Exp $ -->
<guide link="/doc/en/distcc.xml">
@@ -33,8 +33,8 @@
<!-- See http://creativecommons.org/licenses/by-sa/1.0 -->
<license/>
-<version>1.13</version>
-<date>2006-01-25</date>
+<version>1.14</version>
+<date>2006-02-18</date>
<chapter>
<title>Introduction</title>
@@ -246,11 +246,16 @@
<section>
<title>Step 1: Configure Portage</title>
<body>
-
-<p>
-Boot your new box with a Gentoo Linux LiveCD and follow the <uri
-link="/doc/en/handbook/handbook-x86.xml?part=1">installation instructions</uri>
-up until the bootstrapping part. Then configure Portage to use distcc:
+<!--
+Note that this will need to become a link to the old 2005.1 networked handbooks
+once the 2006.0 handbooks are released. Until then, the link can stay.
+-->
+<p>
+Boot your new box with a Gentoo Linux LiveCD and follow the <uri
+link="/doc/en/handbook/handbook-x86.xml?part=1">installation instructions</uri>
+up until the bootstrapping part. (See the <uri
+link="http://www.gentoo.org/doc/en/faq.xml#stage12">Gentoo FAQ</uri> for more
+information about bootstrapping.) Then configure Portage to use distcc:
</p>
<pre caption="Preliminary Setup">
@@ -333,13 +338,13 @@
<chapter>
<title>Troubleshooting</title>
<section>
-<title>Mozilla and Xfree</title>
+<title>Mozilla and Xorg</title>
<body>
<p>
-As you emerge various packages, you'll notice that some of them aren't being
-distributed (and aren't being built in parallel). This is because the
-developers of the Mozilla and Xfree ebuilds intentionally disable parallel
+As you emerge various packages, you'll notice that some of them aren't being
+distributed (and aren't being built in parallel). This is because the
+developers of the Mozilla and Xorg-X11 ebuilds intentionally disable parallel
building because it is known to cause problems.
</p>
@@ -351,27 +356,6 @@
</body>
</section>
<section>
-<title>A Mixture of hardened-gcc and non-hardened-gcc Hosts Will Be Faulty</title>
-<body>
-
-<p>
-With such a long title any explanation here is almost irrelevent. However, if
-you plan to use distcc across hosts that have the <uri
-link="/proj/en/hardened/etdyn-ssp.xml">PaX/hardened-gcc</uri> and some that do
-not, you will run into problems.
-</p>
-
-<p>
-The solution requires a little foresight on your part; you have to run
-<c>hardened-gcc -R</c> on the host that has PaX/hardened-gcc, or you have to
-enable PaX protections in your kernel and <c>emerge hardened-gcc</c>. Both of
-which are a good thing to do since for the most part the protections offered
-by both packages is a good thing and is transparent to the user.
-</p>
-
-</body>
-</section>
-<section>
<title>Mixed GCC Versions</title>
<body>
--
gentoo-doc-cvs@gentoo.org mailing list
next reply other threads:[~2006-02-18 23:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-18 23:21 Josh Saddler [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-04-07 20:57 [gentoo-doc-cvs] cvs commit: distcc.xml Jan Kundrat
2008-01-11 7:05 Joshua Saddler
2007-06-21 23:46 Lukasz Damentko
2006-12-24 17:54 Josh Saddler
2006-09-04 10:23 Josh Saddler
2006-04-04 12:14 Shyam Mani
2006-02-21 16:50 Jan Kundrat
2006-01-25 9:16 Xavier Neys
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200602182321.k1INLjmP016840@robin.gentoo.org \
--to=nightmorph@lark.gentoo.org \
--cc=docs-team@lists.gentoo.org \
--cc=gentoo-doc-cvs@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox