Description

While doing a fresh install of JRuby 1.7.0dev (2012-01-12 11:11 build) and then running update_rubygems (with rubygems-update version 1.3.7 or 1.8.5 - both behave the same), I get the following sigsev error if I use the Oracle JRE7u2 without turning off the invokedynamic:

Joseph Chiu
added a comment - 13/Jan/12 7:26 PM A colleague asked that I try: JAVA_VM="-server" without JAVA_OPTS="-Xcompile.invokedynamic=false" – that also was successful in installing RubyGems without segfaulting.

The master branch has RubyGems 1.8.13, and it has many customizations that we put in so that it works with JRuby. This also includes enhancements like maven integration. By using RubyGems' update facility, you are overwriting those.

Hiro Asari
added a comment - 13/Jan/12 8:12 PM I don't recommend updating RubyGems this way. (Or, updating RubyGems on JRuby in general.)
The master branch has RubyGems 1.8.13, and it has many customizations that we put in so that it works with JRuby. This also includes enhancements like maven integration. By using RubyGems' update facility, you are overwriting those.
$ jruby -v -S gem --version
jruby 1.7.0.dev (ruby-1.8.7-p357) (2012-01-13 694e204) (Java HotSpot(TM) 64-Bit Server VM 1.6.0_29) [darwin-x86_64-java]
1.8.13
Until RubyGems can handle JRuby when it updates, please do not do this.

Joseph Chiu
added a comment - 13/Jan/12 11:49 PM Thank you, Hiro! I apologize that I am coming at this as a fairly new participant to JRuby and Ruby in general.
Given that a number of changes were incorporated to support JRuby, perhaps a special check that generates a warning might be helpful to catch this situation?