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

Greetings, Trying to build core-image-weston from current master fails for gcc 12.2.0-r0 with lots of linker errors. Names of missing functions are strange ala gen_cmulvnx16qi3. In

Current Dev Position: YP 4.1 M4 (Feature Freeze) Next Deadline: 3rd October 2022 YP 4.1 M4 Build Next Team Meetings: Bug Triage meeting Thursday September 29th 7:30 am PDT

There was another thread about sending e-mails with git send-email this week: https://lists.openembedded.org/g/openembedded-core/message/171101 +Robert which pointed to this longer

> PARALLEL_MAKE = "-j ${@int(oe.utils.cpu_count() / 4)}" This won't be optimal in cases where you're rebuilding just one recipe in incremental build which will be finished much faster if you can

Yeah, I'm currently using PARALLEL_MAKE = "-j ${@int(oe.utils.cpu_count() / 4)}" In a .bbappend to limit it, but keep it dynamic. One question out of curiosity or lack of understanding: Bitbake

Do keep in mind that PARALLEL_MAKE can and should be set per recipe, so you can make-limit only the worst items. Alex <Oliver.Westermann@...> wrote:

I expected something like this. Thanks for the confirmation and I will try to play with PARALLEL_MAKE to reduce the impact. - Olli

Hi We are pleased to announce the Yocto Project 4.0.4 Release is now available for

All, YP M+ or high bugs which moved to a new milestone in WW39 are listed below: Priority Bug ID Short Description Changer Owner Was Became High 14065 Automated ptest regression

All, The below were the owners of enhancements or bugs closed during the last week! Who Count yashinde145@... 1 ross.burton@... 1 alejandro@... 1 alexandre.belloni@... 1 Grand