Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Enrico Scholz <enrico.scholz@sigma-chemnitz.de>
To: openembedded-core@lists.openembedded.org
Subject: Re: Broken parallel build of gcc*
Date: Sat, 21 Jul 2012 16:39:05 +0200	[thread overview]
Message-ID: <lyipdhp4ae.fsf@ensc-virt.intern.sigma-chemnitz.de> (raw)
In-Reply-To: <ly629i7inz.fsf@ensc-virt.intern.sigma-chemnitz.de> (Enrico Scholz's message of "Fri, 20 Jul 2012 13:53:36 +0200")

Enrico Scholz
<enrico.scholz-wttK6gPy29v+Hn7q9Vec/7NAH6kLmebB@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. 

The signature stuff was one problem; there is another, more trivial (but
probably more difficult) one:

Adding a task like

| addtask do_rm_old_work before do_unpack

causes stampfile dependencies for the shared gcc like

gcc.do_unpack ->  gcc-initial.do_rm_old_work
gcc.do_unpack ->  gcc-intermediate.do_rm_old_work

E.g. the earlier 'do_rm_old_work' stamps are recipe dependent but the
later 'do_unpack' are shared between recipes. Bitbake reexecutes do_unpack
when the corresponding do_rm_old_work is newer which is causing the seen
errors.

For now, I will declare the task as 'before do_compile'.


Enrico



  parent reply	other threads:[~2012-07-21 14:50 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
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 [this message]
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=lyipdhp4ae.fsf@ensc-virt.intern.sigma-chemnitz.de \
    --to=enrico.scholz@sigma-chemnitz.de \
    --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