Also vulkan-drivers is empty in meson generated by bitbake. If I add it manually it will complain that llvm is disabled. How would I enable it? Am 28. September 2022 10:51:26 MESZ schrieb Alexander

I now have -Dvulkan-drivers=swrast,virtio-experimental In mesa_22.2.0.bb doesn't help Am 28. September 2022 10:51:26 MESZ schrieb Alexander Kanavin <alex.kanavin@...>: -- Diese Nachricht wurde von

I think for software vulkan you need to pass in -Dvulkan-drivers=swrast when building mesa for the target. Alex

I asked the author so I assume he would have told me. Apparently the virglrenderer branch is obsolete. Currently my only changes from poky master are adding vulkan opengl x11 to distro features and

I would first check whether any of that work in the branch has meanwhile landed upstream. The post is from 2021. Have you tried the software Vulkan in the guest? Alex

Khem may be right and it may simply be running out of memory. You could have a look in dmesg and see if the kernel did report OOM conditions. What worries me a little bit is that things corrupted. It

I try to enable vulkan according to this tutorial https://www.collabora.com/news-and-blog/blog/2021/11/26/venus-on-qemu-enabling-new-virtual-vulkan-driver/ According to the author the modified qemu

You need to clarify what you want to do exactly. Why can’t you use the existing recipe? Alex

Greetings, I want to change the git repo url in order to test the Venus driver. Can someone tell me which variable in which recipe I'd have to set? Regards -- Diese Nachricht wurde von meinem

Signed-off-by: Naveen Saini <naveen.kumar.saini@...> --- meta-zephyr-core/lib/oeqa/utils/qemuzephyrrunner.py | 1 + 1 file changed, 1 insertion(+) diff --git

From: Philippe Coval <philippe.coval@...> This Nordic reference design can be a fallback option for Oniro's gateway-blueprint I've been tested it myself along my single arduino-nano

Your machine is fine I think bitbake is extremely parallel and that might be issue that it’s eating up all the memory. How many cores does this machine have? And ram ? Usually it’s good to keep

Hi, Martin create-spdx.bbclass is not from meta-spdxscanner. It comes from poky. If you has any questions about create-spdx.bbclass, I think you can send a mail to the ML of oe-core with a title of "

Yeah building gcc alone worked. Now I'm concerned about the health of my machine. Thank you! Am 27. September 2022 21:02:40 MESZ schrieb Richard Purdie <richard.purdie@...>: -- Diese Nachricht wurde

You are cordially invited to the next OpenEmbedded Happy Hour on September 28 for Europe/Americas time zones @ 1700/5pm UTC (7pm CEST / 1pm ET / 10am

I mean that the build system places more stress on the system than many other workloads and we've sometimes see gcc failures like this as a sign of failing system memory. Running memtest86 might show

<naveen.kumar.saini@...> wrote: Bug opened, https://bugzilla.yoctoproject.org/show_bug.cgi?id=14919

What do you mean with memory issues? Memory broken? Not enough memory? The errors are the same on every run of course I don't build from scratch I just retype bitbake core-image-weston. Gdb also

Hi everyone, I am trying to resolve a dnf package conflicts while trying to perform a dnf upgrade from my old image to my new image. I want to be able to use dnf to upgrade the system. My 2

We build that regularly on the autobuilder so something seems odd here. Could your machine have memory issues? Do you get the same issue each time you build? Cheers, Richard