When building bluecloth with the doc USE flag the build aborts with the following error: /var/tmp/portage/dev-ruby/bluecloth-2.2.0-r1/work/all/bluecloth-2.2.0/Rakefile:25: Use RbConfig instead of obsolete and deprecated Config. Defaulting gemspec to MIT license. Call license in hoe spec to change. /var/tmp/portage/dev-ruby/bluecloth-2.2.0-r1/work/all/bluecloth-2.2.0/Rakefile:25: Use RbConfig instead of obsolete and deprecated Config. Defaulting gemspec to MIT license. Call license in hoe spec to change. rm -rf doc /var/tmp/portage/dev-ruby/bluecloth-2.2.0-r1/homedir/.gem/ruby/1.9.1/bin/rdoc19 --title bluecloth-2.2.0 Documentation -o doc --main README.rdoc lib History.rdoc Manifest.txt README.rdoc README.rdoc History.rdoc rake aborted! Command failed with status (127): [/var/tmp/portage/dev-ruby/bluecloth-2.2.0-...] Tasks: TOP => docs Reproducible: Always Steps to Reproduce: 1. USE=doc emerge -av1 \=dev-ruby/bluecloth-2.2.0-r1 2. rake aborted! 3. Actual Results: Unsuccessful build. Expected Results: Successful build. Looks like the problem is happening in the ruby19 portion of the build. Not sure if that's relevant as I'm sure it's not getting to the ruby20 portion of the build (just a hunch not confirmed).
Created attachment 372816 [details] environment
Created attachment 372818 [details] build.log
Created attachment 372820 [details] emerge --info \=bluecloth-2.2.0
Created attachment 372822 [details] emerge -pqv '=dev-ruby/bluecloth-2.2.0-r1::gentoo'
Created attachment 372824 [details] emerge --info '=dev-ruby/bluecloth-2.2.0-r1::gentoo'
And as the ebuild output requests: GENTOO_VM= CLASSPATH="" JAVA_HOME="/etc/java-config-2/current-system-vm" JAVACFLAGS="" COMPILER=""
Error 127 means command not found. Please give output of: emerge -pv dev-ruby/rdoc Please reinstall dev-ruby/rdoc and try again.
The problem seems to have disappeared after I stopped setting RUBY_TARGETS explicitly. I had previously set it as: RUBY_TARGETS="$RUBY_TARGETS ruby20" If you still want me to dig into this I can but I'm inclined to mark this as resolved.
I've seen the same issue before and so far have blamed newer versions of dev-ruby/hoe, but I can't seem to reproduce this particular failure for bluecloth. Weird.
This should be fixed with hoe 3.11.0.