<html><head></head><body><div>On Fri, 2017-02-03 at 12:29 +0000, Phil Blundell wrote:</div><blockquote type="cite"><div>Ah, right, thanks. The particular piece of magic I was missing was:</div><div><br></div><div> # Nothing need depend on libc-initial/gcc-cross-initial</div><div> if "-initial" in taskdependees[task][0]:</div><div> continue</div><div><br></div><div>which I think explains all the difficulties I was having.</div></blockquote><div><br></div><div>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.</div><div><br></div><div>The problematic recipes are Java ones. The Java toolchain, as you might expect, has a fairly complicated dependency tree but essentially:</div><div><br></div><div>- any Java package has DEPENDS = "virtual/javac-native", which is PROVIDEd by ecj-bootstrap-native.bb</div><div><br></div><div>- 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.</div><div><br></div><div>If I run "bitbake -D -D ..." then I see:</div><div><br></div><div>DEBUG: Added runtime dependencies ['libecj-bootstrap-native'] for .../meta-java/recipes-core/ecj/ecj-bootstrap-native.bb</div><div><br></div><div>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. </div><div><br></div><div>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?</div><div><br></div><div>thanks</div><div><br></div><div>p.</div><div><br></div><div></div></body></html>