From: Albert ARIBAUD <albert.u.boot@aribaud.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v3] Allow for parallel builds and saved output
Date: Tue, 08 May 2012 21:17:37 +0200 [thread overview]
Message-ID: <4FA97151.2090804@aribaud.net> (raw)
In-Reply-To: <201205060348.38731.marex@denx.de>
Le 06/05/2012 03:48, Marek Vasut a ?crit :
> Dear Wolfgang Denk,
>
>> Dear Andy Fleming,
>>
>> In message<1335332031-24138-1-git-send-email-afleming@freescale.com> you
> wrote:
>>> The MAKEALL script cleverly runs make with the appropriate options
>>> to use all of the cores on the system, but your average U-Boot build
>>> can't make much use of more than a few cores. If you happen to have
>>> a many-core server, your builds will leave most of the system idle.
> [...]
>>> MAKEALL | 137
>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++------- 1 files
>>> changed, 122 insertions(+), 15 deletions(-)
>>
>> Applied, thanks.
>
> What do you get if you run:
>
> ./MAKEALL -a arm -l
>
> ? :-)
I am being hit by a spurious build failure in parallel build: pdnb3
succeeds when built alone but fails in a MAKEALL arm with the following
.ERR:
mv: cannot stat
`/home/uboot/src/u-boot-arm/build/pdnb3/include/autoconf.mk.tmp': No
such file or directory
Looks like several builds competed for this temp file name :)...
Amicalement,
--
Albert.
next prev parent reply other threads:[~2012-05-08 19:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-25 5:33 [U-Boot] [PATCH v3] Allow for parallel builds and saved output Andy Fleming
2012-04-25 8:22 ` Albert ARIBAUD
2012-04-25 22:07 ` Andy Fleming
2012-04-30 14:53 ` Wolfgang Denk
2012-05-06 1:48 ` Marek Vasut
2012-05-08 19:17 ` Albert ARIBAUD [this message]
2012-05-08 19:19 ` Andy Fleming
2012-05-08 19:50 ` Marek Vasut
2012-05-08 19:55 ` Andy Fleming
2012-05-18 11:47 ` Wolfgang Denk
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=4FA97151.2090804@aribaud.net \
--to=albert.u.boot@aribaud.net \
--cc=u-boot@lists.denx.de \
/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