> It might be useful to delay backporting this for a bit longer (and I'll soon confirm if 3.10 was already affected or not). I can confirm that 3.10 is also affected. I did build with https://git.open

Hi, it looks like this change is causing mkfs.ext4 to segfault on some builders. I'm seeing it on ubuntu-18.04 (I know it's unsupported now). It might be related to older docker or libseccomp2 there,

Works on gentoo with 13.1.1_p20230520 which was failing before and seems to work with 13.1.1_p20230527 as well (I did only a few builds since upgrade this morning). Thanks Tested-By: Martin Jansa <Mar

The patch author seems a bit mangled by ML, see: author schitrod=cisco.com@... <schitrod=cisco.com@...> 2023-05-27 22:52:52 -0700 https://git.openembedded.org/ope

The BINV needs to match with BASE_VER set in gcc which is 13.1.1 since: https://gcc.gnu.org/git/gitweb.cgi?p=gcc.git;h=2295ad5898aabc652b247446be5769e4a43184f1 otherwise do_install fails. You're right

* since "populate_sdk_base: ensure ptest-pkgs pulls in ptest-runner" change: https://git.openembedded.org/openembedded-core/commit/?id=ecff0642be5781f7f6cca617158b04ac9a0e85f0 in multilib build when b

* pppd was upgraded in: https://git.openembedded.org/openembedded-core/commit/?id=5512bf4dfd299b8d5d474d9f26c2146b3e53514a * connman fails to build with pptp or l2tp PACKAGECONFIG is enabled Signed-of

* use IMAGE_LINK_NAME instead of hardcoding core-image-minimal-${MACHINE} assumption [YOCTO #12937] Signed-off-by: Martin Jansa <Martin.Jansa@...> --- meta/lib/oeqa/selftest/cases/wic.py | 9 +++

Hi, I was able to reproduce it locally and it's caused by newer test (which wasn't merged yet last time I've run selftest with these changes): https://git.openembedded.org/openembedded-core/commit/?id

I was using the same change with locally built uninative-tarball (https://git.openembedded.org/openembedded-core-contrib/log/?h=jansa/master-uninative-3.9-gcc-13) since yesterday and can confirm that

I've recently upgraded by gentoo host to gcc-13.1.1_p20230520 and the just merged gcc-13.1.0 in oe-core isn't new enough for uninative again. This new snapshot started to use ABI from GCC-13.2.0 (as h

and 5.15 kernel bbappend as well (only for rpi builds) ./dynamic-layers/raspberrypi/recipes-kernel/linux/linux-yocto_5.15.bbappend

* we were installing them with -${KERNEL_DTB_NAME} suffix and then adding a symlink without this suffix if KERNEL_IMAGETYPE_SYMLINK is set: if [ "${KERNEL_IMAGETYPE_SYMLINK}" = "1" ] ; then ln -sf $dt

* ${IMAGE_NAME}${IMAGE_NAME_SUFFIX} is almost always used together already and when they aren't it's usually because of hardcoded '.rootfs' suffix * it's a bit strange, because ${IMAGE_NAME_SUFFIX} is

I was using https://github.com/ros/meta-ros/blob/master/scripts/check-patch-files.sh which is far from ideal and has many false positives e.g. you have a .bbappend which sets FILESEXTRAPATHS, but does

Ross, are you going to add REQUIRED_DISTRO_FEATURES = "gobject-introspection-data" to these as well? ERROR: Nothing PROVIDES 'python3-pygobject' (but meta-oe/meta-networking/recipes-connectivity/bluem

* unlike DEPENDS/RDEPENDS the PACKAGE_WRITE_DEPS dependency isn't automatically extended with MLPREFIX, causing lib32-cpio to depend on 64bit ptest-runner (and all its deps) Signed-off-by: Martin Jans

* it was removed from SRC_URI in: https://git.openembedded.org/openembedded-core/commit/?id=1c9cbb27dfe37ca4574c4285fb03ce394dee5ed1 Signed-off-by: Martin Jansa <Martin.Jansa@...> --- .../libglo

* it was removed from SRC_URI in 2015: https://git.openembedded.org/openembedded-core/commit/?id=f80d136bdd578468035a88125fa1b84973fd912b Signed-off-by: Martin Jansa <Martin.Jansa@...> --- meta/

* they were removed from SRC_URI in: https://git.openembedded.org/openembedded-core/commit/?id=41f8760dd8a8ac388389bc17dbc5e0ae0f64bf57 Signed-off-by: Martin Jansa <Martin.Jansa@...> --- ...erfl