Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Phil Blundell <philb@gnu.org>
To: Saul Wold <sgw@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: work-shared not being correctly shared
Date: Mon, 24 Sep 2012 17:22:57 +0100	[thread overview]
Message-ID: <1348503778.31293.52.camel@phil-desktop> (raw)
In-Reply-To: <50607F4E.5040300@linux.intel.com>

On Mon, 2012-09-24 at 08:42 -0700, Saul Wold wrote:
> 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).

Ah, right, it seems to be rm_old_work that's causing the problem.  I'll
disable that for now and figure out how to fix it later.

Thanks

p.





  reply	other threads:[~2012-09-24 16:35 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
2012-09-24 16:22   ` Phil Blundell [this message]
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=1348503778.31293.52.camel@phil-desktop \
    --to=philb@gnu.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=sgw@linux.intel.com \
    /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