too long lines were shrinked: libtool: compile: x86_64-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I/usr/include/dbus-1.0 -I/usr/lib64/dbus-1.0/include -I/usr/include/elogind -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -I/usr/include/sysprof-6 -pthread -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -I/usr/include/sys /bin/sh ./libtool --tag=CC --mode=compile x86_64-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I/usr/include/dbus-1.0 -I/usr/lib64/dbus-1.0/include -I/usr/include/elogind -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -I/usr/include/sysprof-6 -pthread -I/usr/include/glib-2.0 -I/usr/lib64/glib-2. libtool: compile: x86_64-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I/usr/include/dbus-1.0 -I/usr/lib64/dbus-1.0/include -I/usr/include/elogind -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -I/usr/include/sysprof-6 -pthread -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -I/usr/include/sys /bin/sh ./libtool --tag=CC --mode=compile x86_64-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I/usr/include/dbus-1.0 -I/usr/lib64/dbus-1.0/include -I/usr/include/elogind -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -I/usr/include/sysprof-6 -pthread -I/usr/include/glib-2.0 -I/usr/lib64/glib-2. libtool: compile: x86_64-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I/usr/include/dbus-1.0 -I/usr/lib64/dbus-1.0/include -I/usr/include/elogind -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -I/usr/include/sysprof-6 -pthread -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -I/usr/include/sys src/shared/ad.c: In function 'bt_ad_get_name': src/shared/ad.c:1090:24: error: incompatible types when returning type '_Bool' but 'const char *' was expected 1090 | return false; | ^~~~~ ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 23.0_desktop_gnome-20241117-231502 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: 18.1.8 Python 3.12.7 Available Rust versions: [1] rust-bin-1.81.0 [2] rust-bin-1.82.0 * The following VMs are available for generation-2: 1) Eclipse Temurin JDK 21.0.5_p11 [openjdk-bin-21] *) Eclipse Temurin JDK 8.432_p06 [openjdk-bin-8] Available Java Virtual Machines: [1] openjdk-bin-8 system-vm [2] openjdk-bin-21 HEAD of ::gentoo commit 734849484c2f2d30a11c27ea3bc1292bb4cfcc58 Author: Repository mirror & CI <repomirrorci@gentoo.org> Date: Mon Nov 18 08:48:42 2024 +0000 2024-11-18 08:48:41 UTC emerge -qpvO =net-wireless/bluez-5.79 [ebuild N ] net-wireless/bluez-5.79 USE="cups man mesh obex readline udev -btpclient -debug -deprecated -doc -experimental -extra-tools -midi (-selinux) -systemd -test -test-programs" ABI_X86="(64) -32 (-x32)" PYTHON_SINGLE_TARGET="python3_12 -python3_10 -python3_11 -python3_13"
Created attachment 909228 [details] emerge-info.txt
Created attachment 909229 [details] emerge-history.txt
Created attachment 909230 [details] environment
Created attachment 909231 [details] etc.clang.tar.xz
Created attachment 909232 [details] etc.portage.tar.xz
Created attachment 909233 [details] logs.tar.xz
Created attachment 909234 [details] net-wireless:bluez-5.79:20241118-095048.log
Created attachment 909235 [details] qlist-info.txt
Created attachment 909236 [details] temp.tar.xz
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=d2facc542948cfb79193220e7beb9d1c9837df8a commit d2facc542948cfb79193220e7beb9d1c9837df8a Author: Sam James <sam@gentoo.org> AuthorDate: 2024-11-19 03:48:42 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2024-11-19 03:52:22 +0000 sys-devel/gcc: backport C23 fix to 15.0.0_pre20241117 Backport a -std=gnu23/-std=c23 fix to 15.0.0_pre20241117 which prevented coersion from _Bool to NULL. Note that this is still dodgy code and some are proposing this be banned in a future C version (maybe even C2y), but it shouldn't be rejected in this version at least. I've added Closes tags for all bugs which, at a glance, look related, but I haven't re-tested them all and one or two might need reopening. Bug: https://gcc.gnu.org/PR112556 Closes: https://bugs.gentoo.org/943862 Closes: https://bugs.gentoo.org/943861 Closes: https://bugs.gentoo.org/943843 Closes: https://bugs.gentoo.org/943811 Closes: https://bugs.gentoo.org/943809 Closes: https://bugs.gentoo.org/943753 Closes: https://bugs.gentoo.org/943715 Closes: https://bugs.gentoo.org/943704 Closes: https://bugs.gentoo.org/942958 Signed-off-by: Sam James <sam@gentoo.org> ...llow-bool-and-enum-null-pointer-constants.patch | 244 +++++++++++++++++++++ sys-devel/gcc/gcc-15.0.0_pre20241117-r2.ebuild | 54 +++++ 2 files changed, 298 insertions(+)
*** Bug 943811 has been marked as a duplicate of this bug. ***
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=08cc05caea45f6b7c53d95cc5d680055754ef7bb commit 08cc05caea45f6b7c53d95cc5d680055754ef7bb Author: Sam James <sam@gentoo.org> AuthorDate: 2024-11-24 22:29:16 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2024-11-24 22:29:16 +0000 net-wireless/bluez: partly fix C23 compat Noticed when looking at bug #944059. This issue was already fixed by the GCC change referenced in bug #943809 but I already did the work to backport these, so let's pull them in. The issue in bug #944059 is an issue in sys-libs/readline which needs to be addressed separately. Bug: https://bugs.gentoo.org/943809 Bug: https://bugs.gentoo.org/944059 Signed-off-by: Sam James <sam@gentoo.org> net-wireless/bluez/bluez-5.79.ebuild | 3 + net-wireless/bluez/files/bluez-5.79-c23.patch | 123 ++++++++++++++++++++++++++ 2 files changed, 126 insertions(+)
