Weird install issues due to PATH #1

Closed
edubkendo opened this Issue Dec 30, 2012 · 3 comments

Comments

Projects
None yet
2 participants
@edubkendo

Hello, I'm currently running JRuby 1.7.1 with Oracle's Java 7 on Ubuntu 12.04. For unrelated reasons, I have jruby and ruby both installed into my home directory without using rvm or rbenv, so I realize my circumstances are somewhat unusual, but wanted to document this for anyone else who might encounter a similar problem. When I initially ran rake install I got the error uninitialized constant JRUBY_VERSION. Running it as jruby -S rake install appeared to solve the problem, as the install continued without issue, but when I went to run my first example program, jruby hello.rb I got the error LoadError: no such file to load -- jrubyfxml. A little exploration revealed that jruby's rake had installed the gem into my regular ruby's gem directory. Trying to run the example with regular ruby gave me the error cannot load such file -- java,

The whole thing was pretty easily resolved by modifying my path to place JRUBY's bin directory first on my path, before MRI's, which caused the jrubyfxml gem to be installed into jruby's gem directory, and thus I could run jruby hello.rb. I don't know if there's any real issue here, as my use case is probably pretty unusual, but I wanted to document how I resolved it for anyone else encountering the same problem. If I can save them just a few minutes of headscratching.

@byteit101

This comment has been minimized.

Show comment Hide comment
@byteit101

byteit101 Dec 30, 2012

Owner

hmm, interesting. This appears to be caused by bundler exec'ing gem manually without any customization options.

Owner

byteit101 commented Dec 30, 2012

hmm, interesting. This appears to be caused by bundler exec'ing gem manually without any customization options.

byteit101 added a commit that referenced this issue Dec 30, 2012

@byteit101

This comment has been minimized.

Show comment Hide comment
@byteit101

byteit101 Dec 30, 2012

Owner

I've used the internal RubyGems API to build and install now and made a note of your circumstance on the readme, so it should be fixed.

Owner

byteit101 commented Dec 30, 2012

I've used the internal RubyGems API to build and install now and made a note of your circumstance on the readme, so it should be fixed.

@byteit101 byteit101 closed this Dec 30, 2012

@edubkendo

This comment has been minimized.

Show comment Hide comment
@edubkendo

edubkendo Dec 31, 2012

awesome thanks

awesome thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment