From: Anders Darander <anders@chargestorm.se>
To: <openembedded-core@lists.openembedded.org>
Cc: Anders Darander <anders@chargestorm.se>
Subject: [PATCH 0/1] Fix race while building external modules
Date: Wed, 19 Oct 2011 13:14:45 +0200 [thread overview]
Message-ID: <cover.1319022793.git.anders@chargestorm.se> (raw)
When building an image with several external modules, a race is likely to
occur. This race is when building scripts in the staged kernel tree (sysroot).
To prevent this, we promote the do_make_scripts() function to a task, which we
protect by a lock. Tip on how to make this work was received by Richard in
[1]. To avoid new problems, introduced by this promotion, we make this new
task depend on do_populate_sysroot from the modules dependencies
(i.e. virtual/kernel).
This patch has been extensively tested on the 2011-1 release branch, on a
custom ARM-machine and distro with several external modules.
[1] http://lists.linuxtogo.org/pipermail/openembedded-core/2011-October/011163.html
The following changes since commit e31dd9b65f3b03f79cabab25eca157532de3bd9c:
fontconfig: fix fix-pkgconfig.patch (2011-10-18 18:13:47 +0100)
are available in the git repository at:
git://github.com/darander/oe-core ext-mod-race
https://github.com/darander/oe-core/tree/ext-mod-race
Anders Darander (1):
module.bbclass: add lock to prevent error bulding ext modules
meta/classes/module.bbclass | 5 ++++-
1 files changed, 4 insertions(+), 1 deletions(-)
--
1.7.7
next reply other threads:[~2011-10-19 11:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-19 11:14 Anders Darander [this message]
2011-10-19 11:15 ` [PATCH 1/1] module.bbclass: add lock to prevent error bulding ext modules Anders Darander
2011-10-19 11:38 ` Koen Kooi
2011-10-19 11:55 ` Anders Darander
2011-10-20 17:17 ` [PATCH 0/1] Fix race while building external modules Saul Wold
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=cover.1319022793.git.anders@chargestorm.se \
--to=anders@chargestorm.se \
--cc=openembedded-core@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.