Giving docker all 16 GB of memory made the build take 124 minutes. I assume this is due to the VM docker uses fighting for memory with the build and the host, slowing things down. I’m sure someone

Update the installed_OS_is_openembedded check to drop the quotes in the VERSION_ID string to match f451c68667cca of openembedded-core. Without this fix, all tests are reported as

A build flagged for QA (yocto-3.4.2.rc2) was completed on the autobuilder and is available at: https://autobuilder.yocto.io/pub/releases/yocto-3.4.2.rc2 Build hash information: bitbake:

Hi, i am trying to update bbappend files only with SRCREV, SRCBRANCH and SRC_URI defined in bbappend files using devtool .What should i follow Thanks & regards, Manjunath

Ping... any feedback on the patch? If not can it be applied? Thanks :) <snip>

Hello everyone, i hope you are doing well. i am using the command vcgencmd with an image yocto on a raspberry pi zero. I get it by adding the userland recipe. I can get the camera status with the

I agree that a powerful Linux workstation will really help but right nowI do not have access to any of it. I Will try to check if I can get one, but in the meantime I would like to start on my Mac so

Thanks for the pointers, let me try it out on my Mac. Will try to use max cpu cores and RAM to boost the performance a bit. Regards, Abhijeet

<robert.joslyn@...> wrote: Try doing the MBA build with the laptop suspended in the air on a couple of pencils. As the MBA has no fan you might find that increasing airflow around the

I think we should not block the release because of this issue. Thanks, Anuj

<richard.purdie@...> wrote: thanks, sent a fix for diffutils.

A Dockerfile like this works for me: FROM ubuntu:20.04 ARG DEBIAN_FRONTEND=noninteractive ENV LANG=en_US.UTF-8 RUN apt-get update \ && apt-get -y install \ locales \ sudo \ vim-tiny \ &&

Just to give some numbers, building a Dunfell core-image-minimal for the Beaglebone, with a pre-populated DL_DIR took 36 minutes in a Linux VM on a M1 Max Macbook Pro (8 cores, 16GB RAM allocated),

| thread 'main' panicked at 'Failed to find tss2-sys library.: Command { command: "\"pkg-config\" \"--libs\" \"--cflags\" \"tss2-sys\" \"tss2-sys >= 2.3.3\"", cause: Os { code: 2, kind: NotFound,

Drop 001-configure.ac-fix-compatibility-with-autoconf-2.70.patch which is included in update. Signed-off-by: Armin Kuster <akuster808@...> --- ...fix-compatibility-with-autoconf-2.70.patch |

Howdy! While that is perfectly true from the pure technical facts, I have to add that building in Parallels on a M1 is ok-ish. You have to crank up the VM way beyond the defaults, to something like

Even if you do manage to start a build, performance won't be great. Yocto, by design, builds the entire stack from source, so a lot of CPU cores is essential. Don't spend your time waiting, get

Thanks Josef, that sounds like what I want to do isn't really possible Or if it is, it isn't worth the effort.

I initially started with UTM but the problem with virtual machines is that we can only use half the resources of the machine. This makes the builds slower, so I was looking at the container way. Can

With these two patches and the binutils upgrade we see a new issue: https://autobuilder.yoctoproject.org/typhoon/#/builders/89/builds/4733/steps/12/logs/stdio Cheers, Richard