From: Phil Blundell <pb@pbcl.net>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
openembedded-core@lists.openembedded.org
Subject: Re: RSS difficulties
Date: Mon, 06 Feb 2017 13:42:05 +0000 [thread overview]
Message-ID: <1486388525.22715.2.camel@pbcl.net> (raw)
In-Reply-To: <1486124973.13882.29.camel@pbcl.net>
[-- Attachment #1: Type: text/plain, Size: 1540 bytes --]
On Fri, 2017-02-03 at 12:29 +0000, Phil Blundell wrote:
> Ah, right, thanks. The particular piece of magic I was missing was:
>
> # Nothing need depend on libc-initial/gcc-cross-initial
> if "-initial" in taskdependees[task][0]:
> continue
>
> which I think explains all the difficulties I was having.
Actually, that explains most of my difficulties but not all of them.
The remaining ones seem to come down to missing dependencies but I am
not quite clear on why the dependencies are missing.
The problematic recipes are Java ones. The Java toolchain, as you
might expect, has a fairly complicated dependency tree but essentially:
- any Java package has DEPENDS = "virtual/javac-native", which is
PROVIDEd by ecj-bootstrap-native.bb
- ecj-bootstrap-native.bb is basically just a wrapper script which runs
the Java compiler. The actual compiler implementation is in libecj-
bootstrap-native.bb and ecj-bootstrap-native.bb RDEPENDS on that.
If I run "bitbake -D -D ..." then I see:
DEBUG: Added runtime dependencies ['libecj-bootstrap-native'] for
.../meta-java/recipes-core/ecj/ecj-bootstrap-native.bb
but this dependency edge doesn't show up in task-depends.dot and, sure
enough, libecj-bootstrap-native isn't getting installed into the
recipe-sysroot.
Is there some other piece of logic that is squashing these
dependencies? Or is there somewhere else that I ought to be looking
for them?
thanks
p.
[-- Attachment #2: Type: text/html, Size: 2086 bytes --]
next prev parent reply other threads:[~2017-02-06 13:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-03 11:10 RSS difficulties Phil Blundell
2017-02-03 11:20 ` Richard Purdie
2017-02-03 12:29 ` Phil Blundell
2017-02-06 13:42 ` Phil Blundell [this message]
2017-02-06 14:27 ` Richard Purdie
2017-02-06 14:44 ` Phil Blundell
2017-02-06 16:30 ` Phil Blundell
2017-02-06 16:55 ` Phil Blundell
2017-02-06 17:05 ` Burton, Ross
2017-02-06 20:54 ` Khem Raj
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=1486388525.22715.2.camel@pbcl.net \
--to=pb@pbcl.net \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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.