Created attachment 916334 [details] build.log with MAKEOPTS="-j1" CFLAGS="" CXXFLAGS="" # emerge -qpv nokogiri [ebuild U ] dev-ruby/nokogiri-1.16.8 [1.16.6] USE="-doc -test" RUBY_TARGETS="ruby32 -ruby31 (-ruby33)" # MAKEOPTS="-j1" CFLAGS="" CXXFLAGS="" emerge -1 nokogiri (...) >>> Compiling source in /var/tmp/portage/dev-ruby/nokogiri-1.16.8/work ... * Running compile phase for ruby32 make -j1 -Cext/nokogiri V=1 'CFLAGS= -fPIC' 'archflag=-Wl,-O1 -Wl,--as-needed -Wl,-z,pack-relative-relocs' make: Entering directory '/var/tmp/portage/dev-ruby/nokogiri-1.16.8/work/ruby32/nokogiri-1.16.8/ext/nokogiri' x86_64-pc-linux-gnu-gcc -I. -I/usr/include/ruby-3.2.0/x86_64-linux -I/usr/include/ruby-3.2.0/ruby/backward -I/usr/include/ruby-3.2.0 -I. -DHAVE_GUMBO_PARSE_WITH_OPTIONS -DHAVE_XMLHASFEATURE -DHAVE_XMLFIRSTELEMENTCHILD -DHAVE_XMLRELAXNGSETPARSERSTRUCTUREDERRORS -DHAVE_XMLRELAXNGSETVALIDSTRUCTUREDERRORS -DHAVE_XMLSCHEMASETVALIDSTRUCTUREDERRORS -DHAVE_XMLSCHEMASETPARSERSTRUCTUREDERRORS -DHAVE_RB_CATEGORY_WARNING -I/usr/include/libxml2 -I/usr/include -fPIC -o gumbo.o -c gumbo.c gumbo.c:32:10: fatal error: nokogiri_gumbo.h: No such file or directory 32 | #include "nokogiri_gumbo.h" | ^~~~~~~~~~~~~~~~~~ compilation terminated. This is with ruby-3.2.5-r2 and gcc-14.2.1_p20241221. I get the same error compiling nokogiri-1.16.6, which I have successfully emerged on 15 November 2024. GCC 14 happened between then and now... Someone's reported the same issue at: https://forums.gentoo.org/viewtopic-t-1170882.html
Created attachment 916335 [details] emerge --info
I can't reproduce this. This version of gumbo is bundled with nokogiri, and the configure output shows that it is found and prepared, but it looks like the include statement is missing from the CFLAGS. Looking at the build system I don't see an explanation for why that might be missing. Hard to debug this further without being able to reproduce it.
Oh yeah, that path... In fact, every check whether "XY is accepted as CFLAGS/CPPFLAGS" fails there.
Well, the build works now. The CFLAGS/CPPFLAGS checks work normally and the build proceeds. I don't see any strikingly interesting items among the package updates in the past week. But during that time I rebuilt about 130 packages because of a custom USE flags reconfiguration and because of an icu update. Perhaps a related package needed to be rebuilt with the current toolchain. Ruby was one of those 130 packages, I notice. And the last time I had updated it before that was on 12 November, which is before GCC got updated to 14.
