-
Bug
-
Resolution: Unresolved
-
Severe (Users)
-
None
-
None
-
Simply do a world update in next-release with gcc-12.2 active (might also happen with 11 as this doesn't seem to be gcc-related at first glance), pulling in ruby-3.1.3, which then fails to build.
-
Funtoo next users that have a particular defunct or orphaned eselect configured for ruby26, will not be able to merge ruby-3.1.x. All users with Funtoo next installs using the latest Funtoo stage3 should not be impacted by this.
-
Ruby eselect configuration is in a defunct state, leading to later versions of Ruby to use older versions of Ruby went installing with Ruby based scripts
This build failure is occurring on an up-to-date harvester GNOME system, with the only significant deviation from "regular" harvester is that I still have gcc-12.2 enabled.
This is NOT the patch failure that was reported in FL-10771. This is an actual build failure.
Snippet here, and full logs to be attached:
/usr/bin/ruby --disable=gems ./tool/file2lastrev.rb -q --revision.h --srcdir="." > revision.tmp pkg_config= && PKG_CONFIG_PATH=. ${pkg_config:-:} --print-errors ruby.tmp mv -f ruby.tmp.pc ruby-3.1.pc /usr/lib64/ruby/2.6.0/rubygems.rb:16:in `require': ESC[1mcannot load such file -- rubygems/compatibility (ESC[1;4mLoadErrorESC[mESC[1m)ESC[m from /usr/lib64/ruby/2.6.0/rubygems.rb:16:in `<top (required)>' from /var/tmp/portage/dev-lang/ruby-3.1.3/work/ruby-3.1.3/tool/lib/bundled_gem.rb:2:in `require' from /var/tmp/portage/dev-lang/ruby-3.1.3/work/ruby-3.1.3/tool/lib/bundled_gem.rb:2:in `<top (required)>' from -e:1:in `require' make: *** [uncommon.mk:1370: extract-gems-sequential] Error 1 make: *** Waiting for unfinished jobs.... * ERROR: dev-lang/ruby-3.1.3::ruby-kit failed (install phase): * emake failed
