Possible intermittent due to the 3.14 python upgrade? This happened once and did not happen on rebuild: | gcc -Igi/_gi.cpython-314-x86_64-linux-gnu.so.p -Igi -I../sources/pygobject-3.54.5/gi -Isubprojects/pythoncapi-compat -I../sources/pygobject-3.54.5/subprojects/pythoncapi-compat -I/srv/pokybuild/yocto-worker/musl-qemux86-64/build/build/tmp/work/x86_64-linux/python3-pygobject-native/3.54.5/recipe-sysroot-native/usr/lib/pkgconfig/../../../usr/include/python3.14 -I/srv/pokybuild/yocto-worker/musl-qemux86-64/build/build/tmp/work/x86_64-linux/python3-pygobject-native/3.54.5/recipe-sysroot-native/usr/lib/pkgconfig/../../../usr/include/glib-2.0 -I/srv/pokybuild/yocto-worker/musl-qemux86-64/build/build/tmp/work/x86_64-linux/python3-pygobject-native/3.54.5/recipe-sysroot-native/usr/lib/pkgconfig/../../../usr/lib/glib-2.0/include -I/srv/pokybuild/yocto-worker/musl-qemux86-64/build/build/tmp/work/x86_64-linux/python3-pygobject-native/3.54.5/recipe-sysroot-native/usr/lib/pkgconfig/../../../usr/include -fvisibility=hidden -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -isystem/srv/pokybuild/yocto-worker/musl-qemux86-64/build/build/tmp/work/x86_64-linux/python3-pygobject-native/3.54.5/recipe-sysroot-native/usr/include -O2 -pipe -fPIC -pthread -DPY_SSIZE_T_CLEAN -Wall -Warray-bounds -Wcast-align -Wduplicated-branches -Wextra -Wformat=2 -Wformat-nonliteral -Wformat-security -Wimplicit-function-declaration -Winit-self -Wjump-misses-init -Wlogical-op -Wmissing-declarations -Wmissing-format-attribute -Wmissing-include-dirs -Wmissing-noreturn -Wmissing-prototypes -Wnull-dereference -Wold-style-definition -Wpacked -Wpointer-arith -Wrestrict -Wreturn-type -Wshadow -Wsign-compare -Wstrict-aliasing -Wstrict-prototypes -Wswitch-default -Wundef -Wunused-but-set-variable -Wwrite-strings -Wno-missing-field-initializers -Wno-unused-parameter -Wno-discarded-qualifiers -Wno-sign-conversion -Wno-cast-function-type -Wno-int-conversion -fno-strict-aliasing -fvisibility=hidden -MD -MQ gi/_gi.cpython-314-x86_64-linux-gnu.so.p/pygi-resulttuple.c.o -MF gi/_gi.cpython-314-x86_64-linux-gnu.so.p/pygi-resulttuple.c.o.d -o gi/_gi.cpython-314-x86_64-linux-gnu.so.p/pygi-resulttuple.c.o -c ../sources/pygobject-3.54.5/gi/pygi-resulttuple.c | ../sources/pygobject-3.54.5/gi/pygi-resulttuple.c: In function ‘resulttuple_dealloc’: | ../sources/pygobject-3.54.5/gi/pygi-resulttuple.c:337:1: error: label at end of compound statement | 337 | done: | | ^~~~
musl-qemux86-64 debian11-vk-1 agodard/master-next&agodard/master-next-bis completed at 2026-01-16 18:00:41+00:00 https://autobuilder.yoctoproject.org/valkyrie/#/builders/3/builds/3101/steps/12/logs/stdio
May be a generated file and a race.
reproducible debian11-vk-1 agodard/master-next completed at 2026-01-22 17:33:11+00:00 https://valkyrie.yocto.io/pub/repro-fail/oe-reproducible-20260122-dm7ar2y2 https://valkyrie.yocto.io/pub/repro-fail/oe-reproducible-20260122-dm7ar2y2/bitbake-reproducibleA.log https://valkyrie.yocto.io/pub/repro-fail/oe-reproducible-20260122-dm7ar2y2/bitbake-reproducibleB-extended.log https://autobuilder.yoctoproject.org/valkyrie/#/builders/37/builds/3243/steps/13/logs/stdio
Posted "python3-pygobject: fix compile error with old GCC".
(In reply to Ross Burton from comment #4) > Posted "python3-pygobject: fix compile error with old GCC". Should we close this bug?
Yes, thanks.