-
Bug
-
Resolution: Expected Behavior
-
Normal
-
None
-
None
-
None
While installing ruby on a brand new Funtoo Container, I've noticed that merging dev-lang/ruby-2.4.2 ends with a strange error:
usr/lib64/ruby/2.4.0/x86_64-linux/enc/utf_32le.so usr/lib64/ruby/2.4.0/x86_64-linux/enc/windows_1250.so usr/lib64/ruby/2.4.0/x86_64-linux/enc/iso_8859_10.so usr/lib64/ruby/2.4.0/x86_64-linux/enc/gb18030.so usr/lib64/ruby/2.4.0/x86_64-linux/enc/windows_1254.so usr/lib64/ruby/2.4.0/x86_64-linux/enc/gbk.so usr/lib64/ruby/2.4.0/x86_64-linux/enc/windows_1251.so ecompressdir: bzip2 -9 /usr/share/man ecompressdir: bzip2 -9 /usr/share/doc >>> Installing (1 of 14) dev-lang/ruby-2.4.2::ruby-kit !!! Error: Can't load module ruby exiting !!! Error: Can't load module ruby exiting * * To switch between available Ruby profiles, execute as root: * eselect ruby set ruby(19|20|...) * >>> Emerging (2 of 14) dev-ruby/rubygems-2.6.14::ruby-kit * rubygems-2.6.14.tgz SHA256 SHA512 WHIRLPOOL size ;-) ... [ ok ] >>> Unpacking source... >>> Unpacking rubygems-2.6.14.tgz to /var/tmp/portage/dev-ruby/rubygems-2.6.14/work/all >>> Source unpacked in /var/tmp/portage/dev-ruby/rubygems-2.6.14/work >>> Preparing source in /var/tmp/portage/dev-ruby/rubygems-2.6.14/work ... * Running prepare phase for all ... * Running prepare phase for all ... * Adjusting to prefix / * operating_system.rb ... [ ok ] * Running source copy phase for ruby22 ... * Running source copy phase for ruby23 ... * Running source copy phase for ruby24 ... >>> Source prepared. >>> Configuring source in /var/tmp/portage/dev-ruby/rubygems-2.6.14/work ... >>> Source configured. >>> Compiling source in /var/tmp/portage/dev-ruby/rubygems-2.6.14/work ... * Running compile phase for ruby22 ... * Running compile phase for ruby23 ... * Running compile phase for ruby24 ... >>> Source compiled. >>> Test phase [not enabled]: dev-ruby/rubygems-2.6.14 >>> Install rubygems-2.6.14 into /var/tmp/portage/dev-ruby/rubygems-2.6.14/image/ category dev-ruby * Running install phase for ruby22 ... * ERROR: dev-ruby/rubygems-2.6.14::ruby-kit failed (install phase): * $RUBY is not set * * Call stack: * ebuild.sh, line 121: Called src_install * environment, line 4348: Called ruby-ng_src_install * environment, line 4157: Called _ruby_each_implementation 'each_ruby_install' * environment, line 390: Called _ruby_invoke_environment 'ruby22' 'each_ruby_install' * environment, line 511: Called each_ruby_install * environment, line 733: Called doruby '-r' 'rubygems' 'rubygems.rb' 'ubygems.rb' * environment, line 717: Called die * The specific snippet of code: * [[ -z ${RUBY} ]] && die "\$RUBY is not set"; * * If you need support, post the output of `emerge --info '=dev-ruby/rubygems-2.6.14::ruby-kit'`, * the complete build log and the output of `emerge -pqv '=dev-ruby/rubygems-2.6.14::ruby-kit'`. !!! When you file a bug report, please include the following information: GENTOO_VM= CLASSPATH="" JAVA_HOME="" JAVACFLAGS="" COMPILER="" and of course, the output of emerge --info =rubygems-2.6.14 * The complete build log is located at '/var/tmp/portage/dev-ruby/rubygems-2.6.14/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/dev-ruby/rubygems-2.6.14/temp/environment'. * Working directory: '/var/tmp/portage/dev-ruby/rubygems-2.6.14/work/ruby22/rubygems-2.6.14/lib' * S: '/var/tmp/portage/dev-ruby/rubygems-2.6.14/work/ruby22/rubygems-2.6.14' >>> Failed to emerge dev-ruby/rubygems-2.6.14, Log file: >>> '/var/tmp/portage/dev-ruby/rubygems-2.6.14/temp/build.log' * Messages for package dev-lang/ruby-2.4.2: * * To switch between available Ruby profiles, execute as root: * eselect ruby set ruby(19|20|...) * * Messages for package dev-ruby/rubygems-2.6.14: * ERROR: dev-ruby/rubygems-2.6.14::ruby-kit failed (install phase): * $RUBY is not set * * Call stack: * ebuild.sh, line 121: Called src_install * environment, line 4348: Called ruby-ng_src_install * environment, line 4157: Called _ruby_each_implementation 'each_ruby_install' * environment, line 390: Called _ruby_invoke_environment 'ruby22' 'each_ruby_install' * environment, line 511: Called each_ruby_install * environment, line 733: Called doruby '-r' 'rubygems' 'rubygems.rb' 'ubygems.rb' * environment, line 717: Called die * The specific snippet of code: * [[ -z ${RUBY} ]] && die "\$RUBY is not set"; * * If you need support, post the output of `emerge --info '=dev-ruby/rubygems-2.6.14::ruby-kit'`, * the complete build log and the output of `emerge -pqv '=dev-ruby/rubygems-2.6.14::ruby-kit'`. * The complete build log is located at '/var/tmp/portage/dev-ruby/rubygems-2.6.14/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/dev-ruby/rubygems-2.6.14/temp/environment'. * Working directory: '/var/tmp/portage/dev-ruby/rubygems-2.6.14/work/ruby22/rubygems-2.6.14/lib' * S: '/var/tmp/portage/dev-ruby/rubygems-2.6.14/work/ruby22/rubygems-2.6.14' * GNU info directory index is up-to-date.
The weird part is that it continues to try and merge rubygems.
Steps to reproduce
- get a brand new funtoo container
- emerge dev-lang/ruby