From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: bitbake-devel@lists.openembedded.org
Subject: Re: [PATCH] lib/bb/runqueue: avoid marking runtime dependencies as covered
Date: Tue, 15 Nov 2011 11:54:04 +0000 [thread overview]
Message-ID: <1321358044.26881.166.camel@ted> (raw)
In-Reply-To: <1321036695-937-1-git-send-email-paul.eggleton@linux.intel.com>
On Fri, 2011-11-11 at 18:38 +0000, Paul Eggleton wrote:
> The code which populates setscene_covered list was adding a task to the
> covered list if all of the tasks that depend upon it were also covered;
> however, this means that tasks that would have installed "runtime"
> dependencies were being marked as covered also, e.g. gmp-native and
> mpfr-native are needed by gcc-cross at runtime since they are shared
> libraries that gcc links to, but their do_populate_sysroot tasks were
> being marked as covered, resulting in failures later on if gcc-cross was
> available from sstate but mpfr-native and gmp-native weren't.
>
> Since we currently have no real way to handle runtime dependencies for
> native packages, add a workaround which avoids marking tasks as covered
> if one or more of their revdeps are from a different recipe.
>
> Fixes [YOCTO #1536].
>
> Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
> ---
> lib/bb/runqueue.py | 7 ++++++-
> 1 files changed, 6 insertions(+), 1 deletions(-)
Applied to master, thanks.
I have some concerns about this change in that it will cause more "work"
in some cases even where it isn't needed. I'd rather that than the
current situation where we don't install enough of the sstate packages
though.
We're going to have to revisit this at some point but it makes sense to
apply this right now.
Cheers,
Richard
prev parent reply other threads:[~2011-11-15 12:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-11 18:38 [PATCH] lib/bb/runqueue: avoid marking runtime dependencies as covered Paul Eggleton
2011-11-15 11:54 ` Richard Purdie [this message]
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=1321358044.26881.166.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=bitbake-devel@lists.openembedded.org \
--cc=paul.eggleton@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 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.