Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upgraded and moved Rubies, now can't load #66

Closed
trans opened this issue Jan 8, 2013 · 3 comments
Closed

Upgraded and moved Rubies, now can't load #66

trans opened this issue Jan 8, 2013 · 3 comments

Comments

@trans
Copy link

trans commented Jan 8, 2013

I upgraded to the last version, but I also move my rubies from /opt/Ruby to ~/.rubies, now I get:

<internal:gem_prelude>:1:in `require': cannot load such file -- rubygems.rb (LoadError)
    from <internal:gem_prelude>:1:in `<compiled>'
<internal:gem_prelude>:1:in `require': cannot load such file -- rubygems.rb (LoadError)
    from <internal:gem_prelude>:1:in `<compiled>'
@trans
Copy link
Author

trans commented Jan 8, 2013

I'm thinking it might have to do with the fact that I moved my rubies from /opt/Ruby to ~/.rubies, but chruby doesn't seem to completely know it. When I try irb I get:

$ irb
bash: /home/trans/.rubies/1.9.3-p327/bin/irb: /opt/Ruby/1.9.3-p327/bin/ruby: bad interpreter: No such file or directory

@trans
Copy link
Author

trans commented Jan 8, 2013

Yea, okay. So when installing the Ruby it uses --prefix which, it appears, locks it into a specific path and it can't be moved.

@postmodern
Copy link
Owner

Yep, you will have to change the #! lines, as they are hardcoded for MRI.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants