That appears to work for the 2 zephyr machines in meta-arm

Can you try something like this diff --git a/meta/recipes-devtools/gcc/gcc-runtime.inc b/meta/recipes-devtools/gcc/gcc-runtime.inc index 5d74e4494d..61d5bf6058 100644 ---

I haven't had time to bottom out on the issue, but I was able to confirm that the patch in OE core that breaks meta-zephyr is commit 028ecb0c265fa495071cbcca10587c0ba60cf538 Author: Richard Purdie

Hi! It seems that the zephyr build is currently broken with master (and master-next) for meta-zephyr samples: Build Configuration: BB_VERSION = "2.0.1" BUILD_SYS =

mips compiler does not provide intrinsics for 64bit atomics, use libatomics to get them. Signed-off-by: Khem Raj <raj.khem@...> --- meta-oe/recipes-support/poco/poco_1.12.0.bb | 1 + 1 file

It’s already in core, can you just revert these please. Ross From:Khem Raj <raj.khem@...> Date: Monday, 18 July 2022 at 15:46 To: Ross Burton <Ross.Burton@...> Cc: openembedded-devel@...

I wasn't planning to, it has needed a lot of fixes in different places. Where there are good fixes for existing code, we might backport those. Also, just for reference, this QA test already exists

Richard, Any indication this new QA check will be backported to the stable branches? Thanks for the list. -armin

Ah a bit late but we can apply the new fixes once it lands on core

CVE-2014-8180, CVE-2017-18381 and CVE-2017-2665 are not affecting our configuration so they can be safely ignored. Signed-off-by: Davide Gardenal <davide.gardenal@...> ---

> the picobuild 0.2 upgrade queued for oe-core improves “legacy” setuptools builds too. I’ve just looked at the logs and this is the correct fix. Don’t merge these, just wait for picobuild

CVE-2017-8806 doesn't apply to out configuration of postgresql so we can safely ignore it. Signed-off-by: Davide Gardenal <davide.gardenal@...> ---

CVE-2007-2728, CVE-2007-3205 and CVE-2007-4596 are patched in our version of php but they don't have a vulnerable version range in the NVD database, that's why they need to be ignored. Signed-off-by:

This CVE is patched in our version of openjpeg. The NVD database doesn't include a version range this is why it's still reported. Signed-off-by: Davide Gardenal <davide.gardenal@...> ---

This CVE is patched in our version of openjpeg. The NVD database doesn't include a version range this is why it's still reported. Signed-off-by: Davide Gardenal <davide.gardenal@...> ---

Some old CVEs don't have a vulnerable version range in the NVD database, this causes come mismatch with cve-check. Ignore many CVEs that are picked up by the class but are patched in our

CVE-2017-5834, CVE-2017-5835 and CVE-2017-5836 are patched in our version of libplist but they don't have a vulnerable version range in the NVD database, that's why they need to be

Erm, no. python_setuptools_build_meta inherits python_pep517 which does DEPENDS:append = " python3-picobuild-native python3-installer-native” The right fix may be using the setuptools3 class as

OE-Core recently enabled buildpaths in WARN_QA. This is so any reproducibility issues are highlighted by the build much earlier and for a wider cross section of the userbase. We're now at a point

Thanks, To be honest, I didn't test it on this architecture. It's fine, that you've fixed it