public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "W.Kenworthy" <billk@iinet.net.au>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] gcc update failed...
Date: Tue, 07 Jul 2009 09:59:29 +0800	[thread overview]
Message-ID: <1246931969.30061.2.camel@bunyip.localdomain> (raw)
In-Reply-To: <4A527272.4050208@kutulu.org>

On Mon, 2009-07-06 at 17:53 -0400, Mike Edenfield wrote:
> On 7/6/2009 4:23 PM, Jarry wrote:
> > Mike Edenfield wrote:
> >> On 7/6/2009 2:23 PM, Jarry wrote:
> 
> >>> MAKEOPTS="-j2"
> 
> >> Can you try this again without -j2 in the make opts? The gcc build
> >> process is enough of a pain to debug when you can see output
> >> sequentially, running parallel makes makes it worse.
> 
> > Now this is strange: I commented out that MAKEOPTS="-j2" in make.conf
> > and gcc compilled without any complaint. I did not change anything
> > else! Can't believe this. I will check it tomorrow again, with -j2
> > and without...
> 
> I can't explain why this happens but I do know that I've seen a number 
> of complex builds (especially gcc/glibc) that just randomly fail when 
> using a parallel make.  I see this effect on FreeBSD moreso than Gentoo, 
> but I suspect that's only a question of scale.
> 
> --Mike
> 

Try MAKEOPTS="-j1" - the default is still j2 if you just delete the
variable.

Ive also seen this a lot recently.  Serialising the make process into
one thread helps.

BillK






  reply	other threads:[~2009-07-07  1:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-06 17:52 [gentoo-user] gcc update failed Jarry
2009-07-06 18:00 ` Volker Armin Hemmann
2009-07-06 18:05   ` Dale
2009-07-06 18:23   ` Jarry
2009-07-06 18:31     ` Volker Armin Hemmann
2009-07-06 18:53       ` Jarry
2009-07-06 19:08     ` Mike Edenfield
2009-07-06 20:23       ` Jarry
2009-07-06 21:53         ` Mike Edenfield
2009-07-07  1:59           ` W.Kenworthy [this message]
2009-07-07 17:13             ` Jarry

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=1246931969.30061.2.camel@bunyip.localdomain \
    --to=billk@iinet.net.au \
    --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