From: "Xavier Neys (neysx)" <neysx@gentoo.org>
To: gentoo-doc-cvs@lists.gentoo.org
Subject: [gentoo-doc-cvs] gentoo commit in xml/htdocs/doc/en/handbook: hb-install-stage.xml
Date: Mon, 19 Oct 2009 16:16:35 +0000 [thread overview]
Message-ID: <E1MzuuR-0007vi-JP@stork.gentoo.org> (raw)
neysx 09/10/19 16:16:35
Modified: hb-install-stage.xml
Log:
#289741 mention -pipe uses more memory
Revision Changes Path
1.118 xml/htdocs/doc/en/handbook/hb-install-stage.xml
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/hb-install-stage.xml?rev=1.118&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/hb-install-stage.xml?rev=1.118&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/hb-install-stage.xml?r1=1.117&r2=1.118
Index: hb-install-stage.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-stage.xml,v
retrieving revision 1.117
retrieving revision 1.118
diff -u -r1.117 -r1.118
--- hb-install-stage.xml 4 Oct 2009 18:37:42 -0000 1.117
+++ hb-install-stage.xml 19 Oct 2009 16:16:35 -0000 1.118
@@ -4,7 +4,7 @@
<!-- The content of this document is licensed under the CC-BY-SA license -->
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-stage.xml,v 1.117 2009/10/04 18:37:42 nightmorph Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-stage.xml,v 1.118 2009/10/19 16:16:35 neysx Exp $ -->
<sections>
@@ -13,8 +13,8 @@
describe how you extract the stage3 archive and configure Portage.
</abstract>
-<version>10.0</version>
-<date>2009-10-04</date>
+<version>10.1</version>
+<date>2009-10-19</date>
<section>
<title>Installing a Stage Tarball</title>
@@ -411,7 +411,8 @@
<p>
Another popular optimization flag is <c>-pipe</c> (use pipes rather than
temporary files for communication between the various stages of compilation).
-It has no impact on the generated code.
+It has no impact on the generated code, but uses more memory. On systems with
+low memory, gcc might get killed. In that case, do not use this flag.
</p>
<p>
next reply other threads:[~2009-10-19 16:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-19 16:16 Xavier Neys (neysx) [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-03-23 21:45 [gentoo-doc-cvs] gentoo commit in xml/htdocs/doc/en/handbook: hb-install-stage.xml Joshua Saddler (nightmorph)
2011-08-03 8:26 Jan Kundrat (jkt)
2012-10-06 19:49 Sven Vermeulen (swift)
2012-10-31 18:55 Sven Vermeulen (swift)
2012-12-08 18:42 Sven Vermeulen (swift)
2012-12-09 9:21 Joshua Saddler (nightmorph)
2013-01-02 19:06 Sven Vermeulen (swift)
2013-08-03 15:03 Sven Vermeulen (swift)
2013-12-17 10:16 Sven Vermeulen (swift)
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=E1MzuuR-0007vi-JP@stork.gentoo.org \
--to=neysx@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