Only applies when built with ruby USE flag enabled. Element from a meta-bug: See bug# 434064 for details. Reproducible: Always
Please provide the needed details, including emerge --info, build.log currently active and currently installed versions of ruby and any other detail, that helps catching the issue.
Created attachment 324302 [details] emerge --info
Created attachment 324304 [details] Build Log
$ eselect ruby list Available Ruby profiles: [1] ruby18 [2] ruby19 (with Rubygems) * $ equery list ruby * Searching for ruby ... [IP-] [ ] dev-lang/ruby-1.8.7_p370:1.8 [IP-] [ ] dev-lang/ruby-1.9.3_p194-r1:1.9 $ equery -q uses ruby:1.8 +berkdb -debug -doc -examples +gdbm +ipv6 -libedit +ncurses +readline -rubytests -socks5 +ssl +threads -tk -xemacs $ equery -q uses ruby:1.9 +berkdb -debug -doc -examples +gdbm +ipv6 +ncurses +rdoc +readline -rubytests -socks5 +ssl -tk -xemacs +yaml $ RUBYOPT="" emerge subversion ==> results in successful build
Also for this one i asked graff to test subversion-1.7.6 with ruby18 and ruby19 installed and ruby19 as the default ruby provider and he can install it without any issue. Additionally he noted, that the failing part is related to perl, so i suggest you check your perl installation (including perl-cleaner). If the issue afterwards still exists, please provide me with a way to reproduce this or a patch, which fixes it for you, since i cannot reproduce/check this.
It's not perl, but I figured out what is going on. I have the ruby USE flag globally enabled (I do a lot of ruby related work) but I'm trying to use ruby 1.9 over 1.8 when possible. So I have RUBY_TARGETS="ruby19". ruby 1.8 still get pulled in though, by a few packages that do not yet support 1.9. However, since I only have RUBY_TARGETS="ruby19", rubygems does not get built for 1.8, which is what is causing this problem. After adding "dev-ruby/rubygems ruby_targets_ruby18" to /etc/portage/package.use and re-emerging rubygems, subversion emerges correctly.
