Summary: | dev-vcs/subversion-1.7.7 when rubygems isn't installed for ruby18 - .../work/subversion-1.7.7/libtool: line 1130: none: command not found | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | m.unarist |
Component: | [OLD] Development | Assignee: | Thomas Sachau <tommy> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | admwiggin, cornicx, ruby |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | build.log |
Description
m.unarist
2013-01-19 06:25:40 UTC
Created attachment 336092 [details]
build.log
(In reply to comment #0) > Subversion's ruby binding depends dev-lang/ruby:18 only, but its compilation > fails if rubygems isn't installed for ruby18. Can you confirm that this problem is fixed when installing rubygems? > I think this report is same as Bug 167536, but /etc/env.d/10rubygems is > seems to be needed for > ruby19 in my environment. That environment file is shared between ruby implementations to avoid compatibility issues between 1.8 and 1.9 on Gentoo, we can drop it once 1.8 is gone from the tree. If you only install ruby 1.8 you don't technically need this file, but since you also have 1.9 installed this file gets installed and you have this problem with ruby 1.8. @subversion maintainer: subversion still doesn't support ruby 1.9? (In reply to comment #2) > Can you confirm that this problem is fixed when installing rubygems? Yes, I tried below emerging, # USE=ruby RUBY_TARGETS="ruby18 ruby19" emerge -1 rubygems subversion [ebuild R ] dev-ruby/rubygems-1.8.24 RUBY_TARGETS="ruby18*" [ebuild R ] dev-vcs/subversion-1.7.7 USE="ruby*" and it was succeeded. > > I think this report is same as Bug 167536, but /etc/env.d/10rubygems is > > seems to be needed for > > ruby19 in my environment. > > That environment file is shared between ruby implementations to avoid > compatibility issues between 1.8 and 1.9 on Gentoo, we can drop it once 1.8 > is gone from the tree. If you only install ruby 1.8 you don't technically > need this file, but since you also have 1.9 installed this file gets > installed and you have this problem with ruby 1.8. So should I keep rubygems for all installed ruby implementations? (In reply to comment #2) > (In reply to comment #0) > > Subversion's ruby binding depends dev-lang/ruby:18 only, but its compilation > > fails if rubygems isn't installed for ruby18. > > Can you confirm that this problem is fixed when installing rubygems? > > > I think this report is same as Bug 167536, but /etc/env.d/10rubygems is > > seems to be needed for > > ruby19 in my environment. > > That environment file is shared between ruby implementations to avoid > compatibility issues between 1.8 and 1.9 on Gentoo, we can drop it once 1.8 > is gone from the tree. If you only install ruby 1.8 you don't technically > need this file, but since you also have 1.9 installed this file gets > installed and you have this problem with ruby 1.8. > > @subversion maintainer: subversion still doesn't support ruby 1.9? last time i checked: no i committed an updated subversion-1.7.9 ebuild, which requires rubygems[ruby_targets_ruby18] so this should enforce the needed rubygems versions and allow everyone to build subversion with ruby bindings. *** Bug 458940 has been marked as a duplicate of this bug. *** (In reply to comment #4) > (In reply to comment #2) > > (In reply to comment #0) > > @subversion maintainer: subversion still doesn't support ruby 1.9? > > last time i checked: no Note that ruby 1.8 is most likely going away sometime in the summer because at that time upstream will no longer provide support for it. Upstream currently only provides security-related support for this version. (In reply to Thomas Sachau from comment #4) > i committed an updated subversion-1.7.9 ebuild, which requires > rubygems[ruby_targets_ruby18] so this should enforce the needed rubygems > versions and allow everyone to build subversion with ruby bindings. The enforcing works fine, thanks! I close this bug because new discussion about depending ruby1.8 is started in bug 483102. |