Installing Ruby Using Rvm Fails, Without Trace

Installing ruby using RVM fails, without trace

I'll help you in #rvm on irc.freenode.net if you are still stuck. I am in there during the day EST.

Error when installing Ruby 2.1.3 with RVM

I had the same problem

rvm reinstall 2.1.3 --disable-binary

worked for me
(based on Fresh Installs of RVM and Ruby 2.1.1 - dyld library/pathing error).

RVM fails to install Ruby 2.3.x

This took me a while to debug as the log files are not very explicit, most of them point to OpenSSL 1.0 some of them point towards GCC; also this issus can't be reproduced with newer Ruby versions such as 2.4.x.

It seems that the issue is from GCC7 and there is already an official patch released for it.

You can download the patch from https://bugs.ruby-lang.org/attachments/6655/ruby_2_3_gcc7.patch and then run rvm install 2.3.x --patch ruby_2_3_gcc7.patch%0.

This should fix the issue and RVM won't complain anymore.

rvm installation not working: RVM is not a function

You are not using an login shell.

The process of enabling the login flag is described here, also some details on what a login shell is can be found here.

Thus, you need to check the option "Run as login shell" in the Gnome terminal's settings. It is required to open new terminal after this setting the flag.

Sometimes it is required to set the command to /bin/bash --login.

---

For remote connections it is important to understand the differene between running interactive ssh session and executing single commands.

While running ssh server and then working with the server interactively you are using login shell by default and it's all fine, but for ssh server "command" you are not using login shell and it would be required to run it with ssh server 'bash -lc "command"'.

Any remote invocation can have the same problem as executing single command with ssh.

Installing Ruby offline using rvm

I had a similar problem, where I want to deploy the ruby version and all associated gems to the production machines...

I would highly recommend that you use either "rsync' or 'scp -rp' to copy the complete subdirectory ~/.rvm to the target machine. If that machine is completely offline, you could of course copy that directory with 'cp -rp' to a flash-drive and then copy it to the non-networked machine.

One important Gotcha:

be sure that you use the identically named user account on all machines, if you replicate the .rvm directory!

I noticed that the internal book-keeping of RVM keeps track of some environment variables during installation of Ruby versions and gems, and that it keeps track in particular of the name of the user account that was used, and the path to the users's home directory. Beats me why they don't use $HOME and $USER , which are standard on all UNIXes.. seems like a real bug in RVM to me.

if you use the same user account for all machines, it will work just fine.

---

Related Topics