All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: Broken parallel build of gcc*
Date: Fri, 20 Jul 2012 13:04:50 +0100	[thread overview]
Message-ID: <1342785890.21788.10.camel@ted> (raw)
In-Reply-To: <ly629i7inz.fsf@ensc-virt.intern.sigma-chemnitz.de>

On Fri, 2012-07-20 at 13:53 +0200, Enrico Scholz wrote:
> Richard Purdie
> <richard.purdie-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org>
> writes:
> 
> > Encrico: Which DISTRO are you using and do you use rm_work*.bbclass?
> 
> yes; rm_old_work seems to cause the problem.  Task uses ${PN} and was
> declared with
> 
>   addtask rm_old_work before do_unpack
> 
> which causes different base hashes.
> 
> 
> Is there a way to exclude such tasks from the signature handling?

The easiest option is probably something like:

do_rm_old_works[vardepexclude] = "PN"

but this will trigger rebuilds depending on whether rm_work_old is
turned on or off.

The more advanced way to fix this would be in:

http://git.yoctoproject.org/cgit.cgi/poky/tree/meta/lib/oe/sstatesig.py

probably something like:

if dep.endswith("do_rm_old_works"):
    return False

before the first check.

Cheers,

Richard




  reply	other threads:[~2012-07-20 12:16 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-20 10:28 Broken parallel build of gcc* Enrico Scholz
2012-07-20 10:41 ` Martin Jansa
2012-07-20 11:06   ` Richard Purdie
2012-07-20 11:53     ` Enrico Scholz
2012-07-20 12:04       ` Richard Purdie [this message]
2012-07-20 12:15         ` Enrico Scholz
2012-07-20 12:28           ` Richard Purdie
2012-07-20 12:30             ` Martin Jansa
2012-07-20 12:44             ` Enrico Scholz
2012-07-21 14:39       ` Enrico Scholz
2012-07-22  8:43         ` Richard Purdie
2012-07-22  9:43           ` Enrico Scholz
2012-07-22 10:35             ` 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=1342785890.21788.10.camel@ted \
    --to=richard.purdie@linuxfoundation.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 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.