too long lines were shrinked: [83/89] x86_64-pc-linux-gnu-gcc -Ijson-glib/libjson-glib-1.0.so.0.800.0.p -Ijson-glib -I../json-glib-1.8.0/json-glib -I. -I../json-glib-1.8.0 -I/usr/lib64/libffi/include -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -fdiagnostics-color=always -D_F [84/89] x86_64-pc-linux-gnu-gcc -o json-glib/libjson-glib-1.0.so.0.800.0 json-glib/libjson-glib-1.0.so.0.800.0.p/meson-generated_.._json-enum-types.c.o json-glib/libjson-glib-1.0.so.0.800.0.p/json-array.c.o json-glib/libjson-glib-1.0.so.0.800.0.p/json-builder.c.o json-glib/libjson-glib-1.0.so.0.800 [85/89] /usr/lib/python-exec/python3.12/meson --internal symbolextractor /var/tmp/portage/dev-libs/json-glib-1.8.0/work/json-glib-1.8.0-abi_x86_64.amd64 json-glib/libjson-glib-1.0.so.0.800.0 json-glib/libjson-glib-1.0.so.0.800.0 json-glib/libjson-glib-1.0.so.0.800.0.p/libjson-glib-1.0.so.0.800.0.sym [86/89] x86_64-pc-linux-gnu-gcc -o json-glib/json-glib-validate json-glib/json-glib-validate.p/json-glib-validate.c.o -Wl,--as-needed -Wl,--no-undefined -O2 -pipe -march=native -fno-diagnostics-color -Wl,-O1 -Wl,--as-needed -Wl,-z,pack-relative-relocs -Wl,--defsym=__gentoo_check_ldflags__=0 '-Wl,-r [87/89] x86_64-pc-linux-gnu-gcc -o json-glib/json-glib-format json-glib/json-glib-format.p/json-glib-format.c.o -Wl,--as-needed -Wl,--no-undefined -O2 -pipe -march=native -fno-diagnostics-color -Wl,-O1 -Wl,--as-needed -Wl,-z,pack-relative-relocs -Wl,--defsym=__gentoo_check_ldflags__=0 '-Wl,-rpath,$ [88/89] env PKG_CONFIG_PATH=/usr/share/pkgconfig:/var/tmp/portage/dev-libs/json-glib-1.8.0/work/json-glib-1.8.0-abi_x86_64.amd64/meson-uninstalled PKG_CONFIG_LIBDIR=/usr/lib64/pkgconfig PKG_CONFIG=/usr/bin/x86_64-pc-linux-gnu-pkg-config CC=x86_64-pc-linux-gnu-gcc /usr/bin/g-ir-scanner --quiet --no-l FAILED: json-glib/Json-1.0.gir env PKG_CONFIG_PATH=/usr/share/pkgconfig:/var/tmp/portage/dev-libs/json-glib-1.8.0/work/json-glib-1.8.0-abi_x86_64.amd64/meson-uninstalled PKG_CONFIG_LIBDIR=/usr/lib64/pkgconfig PKG_CONFIG=/usr/bin/x86_64-pc-linux-gnu-pkg-config CC=x86_64-pc-linux-gnu-gcc /usr/bin/g-ir-scanner --quiet --no-libtool - ../json-glib-1.8.0/json-glib/json-object.c:944: Warning: Json: invalid "closure" annotation: only valid on callback parameters ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 23.0-20241201-015002 UNMASKED: <sys-devel/gcc-15.0.9999:15 The attached etc.portage.tar.xz has all details. ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-15 * clang version 18.1.8 llvm-config: 19.1.4 Python 3.12.7 go version go1.23.3 linux/amd64 Available Ruby profiles: (none found) Available Rust versions: [1] rust-bin-1.81.0 [2] rust-bin-1.82.0 [3] rust-bin-1.83.0 * The following VMs are available for generation-2: *) Eclipse Temurin JDK 21.0.5_p11 [openjdk-bin-21] Available Java Virtual Machines: [1] openjdk-bin-21 system-vm HEAD of ::gentoo commit 66abdc55a65d46d215ddbaa09dd617427d5c7ff9 Author: Repository mirror & CI <repomirrorci@gentoo.org> Date: Mon Dec 2 16:03:23 2024 +0000 2024-12-02 16:03:22 UTC emerge -qpvO =dev-libs/json-glib-1.8.0 [ebuild N ] dev-libs/json-glib-1.8.0 USE="introspection nls -gtk-doc -test" ABI_X86="(64) -32 (-x32)"
Created attachment 913092 [details] emerge-info.txt
Created attachment 913093 [details] dev-libs:json-glib-1.8.0:20241202-171706.log
Created attachment 913094 [details] emerge-history.txt
Created attachment 913095 [details] environment
Created attachment 913096 [details] etc.clang.tar.xz
Created attachment 913097 [details] etc.portage.tar.xz
Created attachment 913098 [details] logs.tar.xz
Created attachment 913099 [details] qlist-info.txt
Created attachment 913100 [details] temp.tar.xz
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=56bdbdc6e35c38ee9100ea5914edd89d7232d1f7 commit 56bdbdc6e35c38ee9100ea5914edd89d7232d1f7 Author: Sam James <sam@gentoo.org> AuthorDate: 2024-12-02 21:42:02 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2024-12-02 21:43:19 +0000 dev-libs/gobject-introspection: depend on dev-libs/glib[introspection] This should be fine to just do given everything assumes gobject-introspection brings along glib. It's arguably a bit unclean semantically but then so are circular dependencies. Discussed with leio a bit. Bug: https://bugs.gentoo.org/937616 Closes: https://bugs.gentoo.org/945761 Closes: https://bugs.gentoo.org/945748 Closes: https://bugs.gentoo.org/945747 Closes: https://bugs.gentoo.org/945745 Closes: https://bugs.gentoo.org/945742 Signed-off-by: Sam James <sam@gentoo.org> ...spection-1.80.1-r2.ebuild => gobject-introspection-1.80.1-r3.ebuild} | 2 +- ...trospection-1.82.0.ebuild => gobject-introspection-1.82.0-r1.ebuild} | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-)
I have sync'd today and I still have this issue, even though my glib was already built with introspection. If that surprises you, this bug is not yet fixed.
(In reply to Alex Montgomery from comment #11) > If that surprises you, this bug is not yet fixed. I'm not sure this is a useful comment. Anyway, that part is a dupe of bug 945771. *** This bug has been marked as a duplicate of bug 945771 ***
Well, I think it was provably useful in getting this bug which was marked "fixed" as changed to a dupe of a still open bug, don't you?
(In reply to Alex Montgomery from comment #13) > Well, I think it was provably useful in getting this bug which was marked > "fixed" as changed to a dupe of a still open bug, don't you? I just don't think "if that surprises you, ..." really adds anything. The issue here was actually toralf filed a bunch of bugs around the same time and I assumed this one was the same as the others. It ended up being a dupe of what Holger filed.
okay, I was just trying to say that I encountered the bug, did a sync, and then still encountered the bug, even though it was marked fixed. Sorry if my comment was unhelpful. Thank you for what you do, it's very much appreciated.
(In reply to Alex Montgomery from comment #15) > okay, I was just trying to say that I encountered the bug, did a sync, and > then still encountered the bug, even though it was marked fixed. Sorry if my > comment was unhelpful. Thank you for what you do, it's very much appreciated. No worries -- thank you for clarifying, and sorry for being grumpy!
