From: Steffen Sledz <sledz@dresearch.de>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] glibc_2.9: disable parallel make
Date: Mon, 26 Oct 2009 16:29:02 +0100 [thread overview]
Message-ID: <4AE5C03E.2040606@dresearch.de> (raw)
In-Reply-To: <1256570428.9503.235.camel@hammer.suse.cz>
Stanislav Brabec wrote:
> Steffen Sledz wrote:
>> Parallel make for glibc_2.9.bb fails on different multi-cpu build hosts
>> (e.g. AMD Phenom(tm) 9150e Quad-Core Processor running openSUSE 11.1)
>> with various errors. :(
>
> It would make bootstrap longer on multi-CPU machines. :-(
Yes, i know. But i found no other solution for it. :(
> I never seen such failure with PARALLEL_MAKE = "-j 8" and
> BB_NUMBER_THREADS = "8", 8x Xeon, at least with glibc-2.9-r35.2 and not
> before 4249269b.
>
> Does it happen in the same directory every time? Is there any common
> error or missing library?
Sorry, no.
See thread
<http://thread.gmane.org/gmane.comp.handhelds.openembedded/26781>
Steffen
next prev parent reply other threads:[~2009-10-26 15:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-26 14:17 [PATCH] glibc_2.9: disable parallel make Steffen Sledz
2009-10-26 15:20 ` Stanislav Brabec
2009-10-26 15:29 ` Steffen Sledz [this message]
2009-10-27 8:23 ` Steffen Sledz
2009-10-27 19:58 ` Khem Raj
2009-10-28 8:39 ` Steffen Sledz
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=4AE5C03E.2040606@dresearch.de \
--to=sledz@dresearch.de \
--cc=openembedded-devel@lists.openembedded.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