make[2]: Entering directory '/var/tmp/portage/www-servers/h2o-2.2.2/work/h2o-2.2.2_build' cd /var/tmp/portage/www-servers/h2o-2.2.2/work/h2o-2.2.2/deps/mruby && MRUBY_TOOLCHAIN=gcc MRUBY_CONFIG=/var/tmp/portage/www-servers/h2o-2.2.2/work/h2o-2.2.2/misc/mruby_config.rb MRUBY_BUILD_DIR=/var/tmp/portage/www-servers/h2o-2.2.2/work/h2o-2.2.2_build/mruby ruby minirake /usr/lib64/ruby/2.1.0/rubygems.rb:15:in `require': cannot load such file -- rubygems/compatibility (LoadError) from /usr/lib64/ruby/2.1.0/rubygems.rb:15:in `<top (required)>' from <internal:gem_prelude>:1:in `require' from <internal:gem_prelude>:1:in `<compiled>' ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.0-systemd_20170627-203711 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-6.3.0 * Available Python interpreters, in order of preference: [1] python3.4 [2] python2.7 (fallback) Available Ruby profiles: [1] ruby21 *
Created attachment 481348 [details] emerge-info.txt
Created attachment 481350 [details] emerge-history.txt
Created attachment 481352 [details] environment
Created attachment 481354 [details] etc.portage.tbz2
Created attachment 481356 [details] logs.tbz2
Created attachment 481358 [details] temp.tbz2
Created attachment 481360 [details] www-servers:h2o-2.2.2:20170706-040947.log
Hi, Sorry for the issue, but I can't reproduce the issue you had. Please, could you check if the file /usr/lib64/ruby/site_ruby/2.1.0/rubygems/compatibility.rb exist?
Oops: tinderbox@mr-fox ~/img2/17.0-systemd_20170627-203711 $ ls -lR usr/lib64/ruby/site_ruby/2.1.0/ usr/lib64/ruby/site_ruby/2.1.0/: total 0 drwxr-xr-x 1 root root 0 Jun 28 05:10 x86_64-linux usr/lib64/ruby/site_ruby/2.1.0/x86_64-linux: total 0 well, it is a BTRFS fs at a LV; I'll kick of BTRFS entirely soon due to some issues - so do you think, it is a fs issue or a dep issue ?
(In reply to Toralf Förster from comment #9) > > well, it is a BTRFS fs at a LV; I'll kick of BTRFS entirely soon due to some > issues - so do you think, it is a fs issue or a dep issue ? It's probably a dep issue, it seems you don't have dev-ruby/rubygems installed. Which is strange, because it was supposed to be pulled by dev-lang/ruby.