Hi, I am building with my own kernel meta data and that's my little

Yes .. precisely! I'll reply to both email here, so I'm mixing replies to Diego and Kyle throughout. We had a similar discussion in #meta-virt about a month ago, when some AGL builds were running

I've applied your patch, and have pushed it to the repo. I'm also seeing the build failure now. I tried to bump the version of the package, but it still has the same kernel build issue. (my efforts

it builds ok with 5.4 in dunfell now, only gatesgarth with 5.8 and newer with 5.10 kernel are broken

Now with do_patch fixed it fails a bit later in do_compile with: | make[1]: warning: jobserver unavailable: using -j1. Add '+' to parent make rule. | make[1]: Entering directory

* fixes: ERROR: uxen-guest-tools-4.1.7-r0 do_patch: Command Error: 'quilt --quiltrc /OE/build/oe-core/tmp-glibc/work/qemux86_64-oe-linux/uxen-guest-tools/4.1.7-r0/recipe-sysroot-native/etc/quiltrc

Your question made me remember about the docker.scc. Which is being maintained both on meta-virt and yocto-kernel-cache. And linux-yocto_virtualization.inc makes usage of the one from meta-virt, which

Hello, meta-virtualization's linux-yocto_virtualization.inc includes cfg/virtio.scc in KERNEL_FEATURES, which is a dependency from yocto-kernel-cache. However, we do not use yocto-kernel-cache with

In my case it's a custom layer with a recipe that inherits python3native. To reproduce just build python3-native or anything inheriting python3native thus adding python3-native to DEPENDS. The key is

Diego had sent a patch for this earlier today, so I grabbed his and we should be good to go. Bruce <Daniel.Dragomir@...> wrote: -- - Thou shalt not follow the NULL pointer, for chaos and

merged. Bruce In message: [meta-virtualization][PATCH hardknott] busybox-initrd: Update to 1.33.1 on 21/07/2021 Diego Sueiro wrote:

It very likely isn't. The git history shows me wondering that same thing in 2015. When it was introduced, we needed a patch to make the ncurses DEPENDS properly cross compile. That patch is gone, so

For native recipes STAGING_DIR_TARGET = "". This breaks the python3-native build where LIBRARY_PATH ends up being "/lib". Signed-off-by: Ruslan Babayev <fib@...> ---

Just do add. I am not sure why the prepend with export LIBRARY_PATH was added to begin with. Perhaps it is no longer required.

Basically, python3-native recipe with DISTRO_FEATURES with virtualization is broken due to ${STAGING_DIR_TARGET} being undefined and LIBRARY_PATH ending up as "/lib". I can put the part about

You need to elaborate much more in this commit message. We need to document what exactly were the symptoms, in what sort of build things weren't working, and how this fixes it. Cheers, Bruce -- -

Signed-off-by: Ruslan Babayev <fib@...> --- recipes-devtools/python/python3_virtualization.inc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

Hi Bruce! Busybox was upgraded to 1.33.1 for hardknott branch too in oe-core. Can you please backport this patch for hardknott in meta-virtualization? Thanks, Daniel

In oe-core hardknott branch busybox was updated to 1.33.1. Hence, do the same for busybox-initrd recipe. Signed-off-by: Diego Sueiro <diego.sueiro@...> --- .../{busybox-initrd_1.33.0.bb =>

merged. Bruce In message: [meta-virtualization] [PATCH] open-iscsi-user: use update-alternatives for libcap-ng.so on 21/07/2021 wangmy wrote: