From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] gcc fails and then succeeds - definitely a problem?
Date: Thu, 23 Feb 2012 20:38:42 +0000 [thread overview]
Message-ID: <20120223203842.4bf471b2@digimed.co.uk> (raw)
In-Reply-To: <CAN0CFw392c2j9SxBCLTrO4+_zO+d1k-F7UMcPEA8bMsVc9pWGw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 692 bytes --]
On Thu, 23 Feb 2012 11:47:03 -0800, Grant wrote:
> > Parallel builds are not deterministic so if the Makefile allows a race
> > condition to develop it's pot luck whether you'll be hit with it or
> > not
>
> I got sick of stuff like that so I run MAKEOPTS="-j1" on all of my
> systems.
If it were a frequent occurrence, there may be some benefit in that. But
using only one of the CPUs 8 cores is such a waste when this sort of
thing happens only every few weeks. Usually trying again works, rarely
does using -j1 make a difference and when it does a bug report ensures
that it won't be an issue in future.
--
Neil Bothwick
PROSTITUTE: Receiver of swollen goods.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2012-02-23 20:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-23 19:17 [gentoo-user] gcc fails and then succeeds - definitely a problem? Grant
2012-02-23 19:23 ` Michael Mol
2012-02-23 19:40 ` Grant
2012-02-23 21:11 ` Grant
2012-02-23 21:18 ` Mark Knecht
2012-02-23 21:27 ` Alex Schuster
2012-02-23 19:25 ` [gentoo-user] " Heorhi Valakhanovich
2012-02-23 19:28 ` [gentoo-user] " Mark Knecht
2012-02-23 19:36 ` Michael Mol
2012-02-23 19:46 ` Mark Knecht
2012-02-23 21:37 ` Alan McKinnon
2012-02-23 19:39 ` Alan McKinnon
2012-02-23 19:47 ` Grant
2012-02-23 20:38 ` Neil Bothwick [this message]
2012-02-23 21:00 ` Grant
2012-02-23 22:05 ` Michael Mol
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=20120223203842.4bf471b2@digimed.co.uk \
--to=neil@digimed.co.uk \
--cc=gentoo-user@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