Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Phil Blundell <philb@gnu.org>
To: openembedded-core@lists.openembedded.org
Subject: work-shared not being correctly shared
Date: Mon, 24 Sep 2012 16:38:22 +0100	[thread overview]
Message-ID: <1348501103.31293.51.camel@phil-desktop> (raw)

Since updating to the latest versions of bitbake and oe-core I'm
experiencing some sort of conflict to do with the gcc sources in
tmp/work-shared.

What seems to be happening is that all the different recipes which share
that source directory are using different stamp values for do_unpack.
So, for example, I can do:

$ bitbake -f -c unpack gcc-cross
[ source unpacks ]
$ ls -l tmp-eglibc/stamps/work-shared/gcc-4.7.2-r13.do_unpack*
-rw-rw-r-- 1 pb pb 0 2012-09-24 15:37
tmp-eglibc/stamps/work-shared/gcc-4.7.2-r13.do_unpack.ea6dd89ddae3dcc205848b41ce0251cd
$ bitbake -f -c unpack gcc-cross
[ nothing happens ]
$ bitbake -f -c unpack gcc-cross
[ still nothing happens ]
$ bitbake -f -c unpack gcc-runtime
[ source unpacks again ]
$ ls -l tmp-eglibc/stamps/work-shared/gcc-4.7.2-r13.do_unpack*
-rw-rw-r-- 1 pb pb 0 2012-09-24 15:42
tmp-eglibc/stamps/work-shared/gcc-4.7.2-r13.do_unpack.e677db6d46e8c0c6109b02302aa477d0
$ bitbake -f -c unpack gcc-runtime
[ nothing happens ]

Worse, if I set BB_NUMBER_THREADS to some high number, I seem to end up
with multiple competing tasks all trying to unpack in parallel and the
build never makes any real forward progress.

Does anybody have any insight into what is going wrong here and how I
should debug it?

thanks

p.





             reply	other threads:[~2012-09-24 15:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-24 15:38 Phil Blundell [this message]
2012-09-24 15:42 ` work-shared not being correctly shared Saul Wold
2012-09-24 16:22   ` Phil Blundell
2012-09-24 19:28     ` Martin Jansa
2012-10-01 11:50       ` Phil Blundell
2012-10-01 13:38         ` Richard Purdie

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=1348501103.31293.51.camel@phil-desktop \
    --to=philb@gnu.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox