Created attachment 918319 [details] build.log > >>> Compiling source in /var/tmp/portage/app-text/tree-2.1.1-r1/work/unix-tree-2.1.1 ... > make -j16 CC=x86_64-pc-linux-gnu-gcc 'CFLAGS=-O2 -pipe -march=znver5 -mno-prefetchi -mshstk --param=l1-cache-line-size=64 --param=l1-cache-size=48 --param=l2-cache-size=1024 -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE' 'LDFLAGS=-Wl,-O1 -Wl,--as-needed -Wl,-z,pack-relative-relocs' > x86_64-pc-linux-gnu-gcc -O2 -pipe -march=znver5 -mno-prefetchi -mshstk --param=l1-cache-line-size=64 --param=l1-cache-size=48 --param=l2-cache-size=1024 -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -c -o unix.o unix.c > In file included from unix.c:18: > tree.h:85:30: error: expected ‘;’, identifier or ‘(’ before ‘bool’ > 85 | typedef enum {FALSE=0, TRUE} bool; > | ^~~~ > tree.h:85:30: warning: useless type name in empty declaration > make: *** [Makefile:100: unix.o] Error 1 > make: *** Waiting for unfinished jobs.... This is fixed in app-text/tree-2.2.1
Created attachment 918320 [details] emerge --info
> This is fixed in app-text/tree-2.2.1 For these bugs, I wouldn't worry about filing for them if they're fixed in ~arch, unless there's some reason (like say, the stable version vs ~arch version being some huge rewrite we may not want to stable for *ages*) that we may want to backport the fix. They'll trickle down naturally long before GCC 15 is even keyworded. There's also the general issue for stable packages where we may commit runtime fixes in a new revision in ~arch but not stable yet in case there's some risk of breakage.
