From: Saul Wold <sgw@linux.intel.com>
To: Phil Blundell <philb@gnu.org>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: work-shared not being correctly shared
Date: Mon, 24 Sep 2012 08:42:06 -0700 [thread overview]
Message-ID: <50607F4E.5040300@linux.intel.com> (raw)
In-Reply-To: <1348501103.31293.51.camel@phil-desktop>
On 09/24/2012 08:38 AM, Phil Blundell wrote:
> 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?
>
Yes, I am seeing something similar with do_patch happening twice on the
work-shared area, I talked with Richard a bit ago about it, and I am
digging into the siginfo files, you can use bitbake-sigdiff to see what
sigs are changed causing it unpack twice (or in my case patch twice).
Sau!
> thanks
>
> p.
>
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
>
next prev parent reply other threads:[~2012-09-24 15:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-24 15:38 work-shared not being correctly shared Phil Blundell
2012-09-24 15:42 ` Saul Wold [this message]
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=50607F4E.5040300@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=philb@gnu.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.