[yocto] u-boot recipe: Missing dependencies

Burton, Ross ross.burton at intel.com
Mon Oct 9 03:30:09 PDT 2017


On 8 October 2017 at 18:04, Eric Schwarz <eas at sw-optimization.com> wrote:

> Don't _append when you can just extend the assignment above.
>>
>
> I just did it that way for the moment since I wanted to circumvent merge
> conflicts when I upgrade the underlying recipes from openembedded.


Well it's ugly, so if you want a patch in oe-core then don't introduce ugly
for your convenience.


> Depending on python-native does nothing as the binary isn't in $PATH still.
>>
>
> I thought any Yocto native binaries built are in the PATH automatically. -
> How
> to fix this/do it correctly?
>

You need to inherit python3native, as python (and some others) are opt-in.


> Can you provide a configuration to make U-Boot build on x86 for testing?
>>
>
> I put now some patches in ordered manner on top of the original recipes
> from
> openembedded.
> However, before sending I would like to fix two issues so the recipes can
> go
> into mainline immediately.
>
> 1.) I am working w/ -morty Yocto branch at the moment. The 'u-boot.inc'
> from
>     openembedded does not work w/ -morty.
>     I get the following error "AttributeError: module 'bb.utils' has no
>     attribute 'filter'". Building w/ the original -morty 'u-boot.inc'
> works.
>

Yes, bb.utils.filter() is a new function that isn't in morty.

Ross
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/yocto/attachments/20171009/fe221c7e/attachment.html>


More information about the yocto mailing list