Greetings, I tried to run an Aarch64 Yocto with qemu on amd 64 Host. For that purpose, I built core-image-weston from Hardknott following the

Yes, I am building Yocto inside docker containers. But previously, I did not face this issue with docker container.

Are you running in a virtual machine of some kind? It's better to get a real linux computer. Otherwise you need to check how to allocate more disk space to the virtual machine from the host. Alex

Hi Alex, Below is the output of "df":

Can you show the output of 'df' please? Alex

Hello, Thanks for the update. Even after deleting build/tmp and build/sstate-cache and setting `INHERIT += "rm_work"` in the build/conf/local.conf. But still I am facing same issue. Is there any way

Hi there, Is there anything pending here from our side? Can someone let us know by when this patch can be merged? Thanks, Ranjitsinh Rathod

Only the last two. Deleting tmp/ does help as then any needed binary items will be taken from sstate cache instead of being unpacked from source and rebuilt. Alex

Hi Quentin, Too late to give you a "Reviewed-by", but thanks for the corrections and simplifications! Cheers Michael. -- Michael Opdenacker, Bootlin Embedded Linux and Kernel

Am Mi, 16. Mär 2022, um 08:54, schrieb Sourabh Hegde: These directories are crucial for a yocto build and they will get recreated if not existing. Deleting them does nothing besides prolonging the

Hi, This is a common problem. I run to this almost weekly basis doing a lot yocto compiles on my developer machine. Solution for me is to manually check before compiling that I still have 100's

Hello All, I am using Yocto for one of my project. I know that Yocto needs a good amount of disk space for build activities. And also I am working as non-root user in Ubuntu 20.04. But I often run

It's not about glibc version used in target builds on dunfell, but about glibc version used to build uninative tarball. If you're using older docker daemon to run your builds, then easiest fix is to

Hi all, my dunfell build for a NVIDIA Jetson TX2 (support from meta-tegra) is failing in the way described here: https://lists.yoctoproject.org/g/yocto/topic/86571641#55134. As per a comment of

Looks like the libraries are unversioned. This is pretty bad practise but https://docs.yoctoproject.org/dev-manual/common-tasks.html#working-with-pre-built-libraries should help. The best solution

Thanks again...

From: Quentin Schulz <quentin.schulz@...> The patch was meant as a quick temporary work-around to have the docs built and published. Now that releases where -W flag is set (turning

From: Quentin Schulz <quentin.schulz@...> The patch was missing from yocto-3.4.1 release and only made it to yocto-3.4.2 unfortunately so let's backport it. Cc: Quentin Schulz

From: Quentin Schulz <quentin.schulz@...> Each Yocto Project release is validated for a specific Bitbake release. By mistake, most release docs are pointing at the development

From: Quentin Schulz <quentin.schulz@...> There's no need to keep a list of tags requiring to be patched since the tag is part of the path where patches are stored. Therefore,