Skip to contentSkip to conversation

u-boot recipe: Missing dependencies

PATCH Eric Schwarz 3 participants 6 messages Oct 3, 2017 – Nov 8, 2017

lore
Share & tools
lore
#0 lore raw

Hello,

it seems that even in the most current yocto u-boot recipes from openembedded some general and also x86 specific dependencies are missing. The patch below adds them.

From 0502033c5e555abaadcb5e01faae041293edddd9 Mon Sep 17 00:00:00 2001
From: Eric Schwarz <[email protected]>
Date: Tue, 3 Oct 2017 18:24:51 +0200
Subject: [PATCH] u-boot: u-boot_2017.09.bb: ARRI adaptations.

- Add missing dependencies.

---
 recipes-bsp/u-boot/u-boot_2017.09.bb | 2 ++
 1 file changed, 2 insertions(+)
recipes-bsp/u-boot/u-boot_2017.09.bb +2 -0
index 37c21dc..a676252 100644
@@ -2,3 +2,5 @@ require u-boot-common_${PV}.inc
 require u-boot.inc
 
 DEPENDS += "bc-native dtc-native"
+DEPENDS_append = " python-native"
+DEPENDS_append_x86-64 = " iasl-native swig-native"

--
2.7.4

Cheers
Eric

#1 lore raw

recipes-bsp/u-boot/u-boot_2017.09.bb require u-boot-common_${PV}.inc · line 6

Quoted 4 lines · Eric Schwarz

DEPENDS += "bc-native dtc-native"

recipes-bsp/u-boot/u-boot_2017.09.bb +2 -0
+DEPENDS_append = " python-native"
+DEPENDS_append_x86-64 = " iasl-native swig-native"

Don't _append when you can just extend the assignment above.

Depending on python-native does nothing as the binary isn't in $PATH still.

Can you provide a configuration to make u-boot build on x86 for testing?

Ross

#2 lore raw

Hi Ross,

Quoted 5 lines

recipes-bsp/u-boot/u-boot_2017.09.bb require u-boot-common_${PV}.inc · line 6

Quoted 3 lines

DEPENDS += "bc-native dtc-native"

recipes-bsp/u-boot/u-boot_2017.09.bb +2 -0
+DEPENDS_append = " python-native"
+DEPENDS_append_x86-64 = " iasl-native swig-native"

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.

Quoted 1 line

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?

Quoted 1 line

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.
2.) There is an issue w/ the U-Boot build system that it needs the "libgcc.a"
from the local host system [1]. I circumvented this by checking in
my
"libgcc.a" and patching the U-Boot makefile accordingly. This must
be
fixed in U-boot.

[1]... https://www.mail-archive.com/[email protected]/msg36721.html

Cheers
Eric

#3 lore raw
Quoted 5 lines · Eric Schwarz

Don't _append when you can just extend the assignment above.

Quoted 1 line

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.

Quoted 7 lines

Depending on python-native does nothing as the binary isn't in $PATH still.

Quoted 1 line

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.

Quoted 10 lines

Can you provide a configuration to make U-Boot build on x86 for testing?

Quoted 1 line

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.

Quoted 7 lines

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

#4 lore raw

Be aware that when you provide python-native, it's more likely that swig-native will be detected in sysroot as well and then u-boot will fail to build libfdt python library.

To prevent this autodetection you can use something like this:

do_compile_prepend () {
    sed 's@\(^always += $(if $(shell which swig 2>
/dev/null),_libfdt.so)$\)@# do not autodetect swig, there is no swig-native
dependency \1@g' -i ${S}/tools/Makefile
}

which isn't needed in Yocto 2.3 Pyro and newer thanks to RSS and HOSTTOOLs filtering.

Quoted 54 lines · Ross
Quoted 5 lines · Eric Schwarz

Don't _append when you can just extend the assignment above.

Quoted 1 line

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.

Quoted 8 lines

Depending on python-native does nothing as the binary isn't in $PATH

Quoted 2 lines

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.

Quoted 10 lines

Can you provide a configuration to make U-Boot build on x86 for testing?

Quoted 1 line

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.

Quoted 7 lines

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

--
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto

#5 lore raw
In reply to Burton, Ross
Quoted 8 lines

Am 09.10.2017 12:30, schrieb Burton, Ross:

Quoted 4 lines · Eric Schwarz

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.

Well, I have only done this, so the patch does apply the next time. Since in case someone changes something in the mainline it is always a hassle otherwise. For the final version it will be fixed.

Quoted 5 lines
Quoted 3 lines
Quoted 1 line

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.

Well, okay, but WTH I do not need to inherit from something for "bc-native" and "dtc-native"?

Eric