From: Nathanael Nerode <neroden@twcny.rr.com>
To: gcc-patches@gcc.gnu.org, binutils@sources.redhat.com,
gdb-patches@sources.redhat.com
Subject: Configure serialization & company
Date: Mon, 30 Dec 2002 06:06:00 -0000 [thread overview]
Message-ID: <20021230104112.GA382@doctormoo> (raw)
All right.
How about a note about parallel builds in the installation manual.
"If you intend to do a parallel build and you are concerned about some
(very unlikely) race conditions in 'configure', we suggest that you do
configure
make -j1 configure-build
make -j6000 all-build
make -j1 configure-host
make -j6000 all-host
make -j1 configure-target
make -j6000 all-target"
Or something like that. And fix up the Makefile so that one can
actually do that (which is not much work at all).
Personally, I think that should suffice. :-/
Other people agree?
--Nathanael
reply other threads:[~2002-12-30 10:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20021230104112.GA382@doctormoo \
--to=neroden@twcny.rr.com \
--cc=binutils@sources.redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb-patches@sources.redhat.com \
/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