[poky] Dependency problem

Jussi Kukkonen jussi.kukkonen at intel.com
Wed Sep 6 01:15:41 PDT 2017


On 5 September 2017 at 19:49, Koeller, Thomas <Thomas.Koeller at baslerweb.com>
wrote:

> You didn't mention the Yocto version. Sysroot functionality has changed
> quite a bit in recent releases so you should do that. The changes also mean
> that unusual
> > sysroot tricks written a few releases back will not work as is on more
> recent releases. See
> > http://www.yoctoproject.org/docs/current/ref-manual/ref-
> manual.html#migration-2.3-recipe-specific-sysroots for more details
>
> BitBake tells me that I am on version 1.28.
>


Bitbake 1.28 was included in Yocto 2.0 which is four releases (or two
years) behind latest release: This means the recipe specific sysroots are
not something you need to care about (and also that you need to be careful
to not follow current documentation regarding sysroots).


> On latest release "bitbake -g -u taskexp recipe-a" will give you a UI for
> browsing task dependencies. You should find "recipe-a.do_configure"
> depending
> > "recipe-a.do_prepare_recipe_sysroot", and that depending on
> "recipe-b.do_populate_sysroot". If this is not the case then it seems
> likely something in the recipe
> > (or its inherits) is undoing that dependency.
>
> I got a step further. Looking at the log files produced by building
> recipe_a, I cannot find one for the do_configure task, which seems to
> indicate that no
> such task was ever executed. This would explain why the dependency did not
> work, but leads to the question why do_configure did not run.
> Any idea where I should look?
>

This is probably something your recipe does (e.g. via inheriting
bin_package or maybe using do_configure[noexec] = "1". You'll have to
decide if the missing do_configure is intended and if it is, maybe look at
the dependency chain of the task that actually fails because sysroot isn't
populated.

I'd really like to suggest putting effort into fixing the legal issues that
prevent you from sharing your recipes... There may be people on this list
who can debug issues like this without seeing the recipe but I can
understand how it feels like a bad use of their time and I hope you can too.

Cheers,
  Jussi
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/poky/attachments/20170906/65a6678d/attachment.html>


More information about the poky mailing list