From: Albert ARIBAUD <albert.u.boot@aribaud.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] Builds in MAKEALL -a arm failing sometimes when BUILD_NBUILDS>1?
Date: Sat, 9 Feb 2013 08:38:42 +0100 [thread overview]
Message-ID: <20130209083842.03aa5673@lilith> (raw)
Hello,
... this time from the present.
Recently I have seen MAKEALL -a arm fail sporadically on some boards
during parallel builds; more specifically, with BUILD_NBUILDS=8 and
BUILD_NCPUS=1.
Has anyone seen this, or is anyone working on MAKEALL arm now and
willing to give a look?
Note that the actual machine has a 4-core, 8-thread CPU, so maybe that
was because the number of parallel builds was just equal to the number
of (pseudo) CPUs available; I am now using six parallel builds and
haven't seen the issue again so far.
On second (and slightly more caffeinated) thought, it could be related
to building variants of a single target in boards.cfg -- maybe when
cleaning files for one variant while another one is being built.
(also, I prepend the command with LANG=C to avoid making the error
messages any more French than they already are when I copy-paste them
to the list. Not sure how that could have any influence on the build
errors, of course.)
Amicalement,
--
Albert.
reply other threads:[~2013-02-09 7:38 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=20130209083842.03aa5673@lilith \
--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