Can we pass this through some variable (maybe even as default EXTRA_OESCONS)? Some recipes seem to use older scons which don't support this and fail with: Unknown variables: MAXLINELENGTH ERROR: scons

* True is default since 2016 and most layers were already updated not to pass this parameter where not necessary, e.g. oe-core was updated couple times, first in: https://git.openembedded.org/openembe

On Tue, Jan 31, 2023 at 8:18 AM Martin Jansa via lists.openembedded.org <Martin.Jansa=gmail.com@...> wrote: I can confirm it fails the same with this commit from Hitendra in dunfell

I haven't checked yet in dunfell, but in kirkstone this commit merged last week breaks nativesdk-qemu builds. This chunk: +@@ -1486,7 +1505,7 @@ void *qxl_phys2virt(PCIQXLDevice *qxl, QXLPHYSICAL pqxl

* most xinetd users probably don't need this nowadays and it pulls perl into the images Signed-off-by: Martin Jansa <Martin.Jansa@...> --- meta/recipes-extended/xinetd/xinetd_2.3.15.4.bb | 5 +++

FWIW: this change doesn't help in the case I've reported earlier, because the bbclass which was doing the split('-') was also checking that the suffix was one of the supported values. So I'll continue

git log --oneline contrib/lucaceresoli/master-next -- meta/recipes-graphics/mesa/ | head -n 3 8b328a698cc mesa: update submitted patch with backported version ab86331bf4a mesa: allow mesa (gbm) to com

Samuli: Similar mesa upgrade was merged recently: https://git.openembedded.org/openembedded-core/commit/?id=3bf4341ef6a681574a1c6f393bf241f412e26eac qtbase still fails the same, more details in: https

Kai: can you please test it on ubuntu-18.04? I've tested it with DEBUG_BUILD in native and target build on a host with new toolchain (gentoo with gcc-12.2.1) and according to https://gitlab.freedeskto

* this version was merged to main in: https://gitlab.freedesktop.org/mesa/mesa/-/commit/267dd1f4d571ee606141aa66f1665aa152b4e911 and cherry-picked to staging/23.0 as well in: https://gitlab.freedeskto

> Not sure why this didn't show up in my testing! It's shown only when do_patch task is really executed and it doesn't cause the do_patch to fail completely. So it's possible that you've built it once

The use case I was fixing in: https://git.openembedded.org/openembedded-core/commit/?id=f40a2658f5be6739c5dddab7f9f11e1f85a17102 was just about rpmdeps not being able to find rpmrc due to wrong path i

* the last patch added in: https://git.openembedded.org/openembedded-core/commit/?h=kirkstone&id=874b72fe259cd3a23f4613fccfe2e9cc3f79cd6a doesn't apply cleanly. * fixes: ERROR: ffmpeg-5.0.1-r0 do_patc

This patch doesn't apply cleanly on ffmpeg-5.0.1: ERROR: ffmpeg-5.0.1-r0 do_patch: Fuzz detected: Applying patch 0001-avcodec-vp3-Add-missing-check-for-av_malloc.patch patching file libavcodec/vp3.c H

Acked-by: Martin Jansa <Martin.Jansa@...>

There is also separate issue that VirtualBox CPU doesn't support fma, f16c. e.g.: root@qemux86-64:~# mediaindexer Incompatible processor. This Qt build requires the following features: fma f16c There

* use Skylake-Client to match QB_CPU_KVM as changed in: https://git.openembedded.org/openembedded-core/commit/?id=6f2af1e5d1537b4d31e14946292bf58f0fd76fc9 * explicitly set -cpu instead of letting qemu

FWIW: here is the earlier (2014) discussion about this: https://lore.kernel.org/all/1414675717.7649.56.camel@ted/

* CVE-2022-45873.patch was backported from systemd/main, but it doesn't build without another change from v252 when elfutils PACKAGECONFIG is enabled. * fixes: | ../git/src/shared/elf-util.c: In funct

I'm a bit late, but this change seems to cause: | ../git/src/shared/elf-util.c: In function 'parse_elf_object':| ../git/src/shared/elf-util.c:792:27: error: void value not ignored as it ought to be |