- 1 Installing RVM
- 2 Post installation
- 3 Using RVM
- 4 Further Reading
- 5 Troubleshooting
The install process is very easy, and is the very same for any distro, including ArchLinux. You have two choices, one system-wide, another as a user. The first is for production servers, or if your are alone on your machine. You'll need root privileges. The second is the recommended for multiple users on the same machine (like a development test box). If you do not know which to choose, start with a single user installation.
The upstream instructions for installing RVM should just work. The install script is aware enough to tell you what packages you need to install on Archlinux to make different rubies work. This usually involves gcc and some other stuff needed to compile ruby.
As an observation, installing RVM with gem is not recommended anymore. This article uses the recommended documentation with minor tweaks to make work on ArchLinux.
Before we start, we'll need the following to get the installation process going:
$ pacman -S git curl
We will use the script that rvm docs recommends to install. Make sure to run this script as the user for whom you want RVM installed (i.e. your normal user that you use for development).
$ bash < <( curl -s https://rvm.beginrescueend.com/install/rvm )
If instead you want to check the script before running it, do:
$ curl -L https://rvm.beginrescueend.com/install/rvm > rvm-install
Inspect the file, then run it with:
$ bash < ./rvm-install
After the script has finished, then add the following line to the end of your ~/.bash_profile or ~/.bashrc (or ~/.zprofile or whatever):
$ [[ -s "$HOME/.rvm/scripts/rvm" ]] && source "$HOME/.rvm/scripts/rvm"
System-wide installation is a similar procedure to the single user install. However, instead run the install script with sudo. Do not run the installer directly as root!
$ sudo bash < <(curl -s https://raw.github.com/wayneeseguin/rvm/master/binscripts/rvm-installer )
After the script has finished, add your users to the 'rvm' group. (The installer does not auto-add any users to the rvm group. Admins must do this.) For each user, repeat:
$ sudo usermod -a -G rvm <user>
Group memberships are only evaluated at login time. Log the users out, then back in.
Close out your current shell or terminal session and open a new one. You may attempt reloading your .bash_profile with the following command:
$ source .bash_profile
However, closing out your current shell or terminal and opening a new one is the preferred way for initial installations.
RVM will be automatically configured for every user on the system; this is accomplished by loading /etc/profile.d/rvm.sh on login. Archlinux defaults to parsing /etc/profile which contains the logic to load all files residing in the /etc/profile.d/ directory.
Finally, see if there are any dependency requirements for your installation by running:
$ rvm requirements
You only use the sudo command during the install process. In Multi-User configurations, any operations which require sudo access must use the rvmsudo command which preserves the RVM environment and passes this on to sudo. There are very few cases where rvmsudo is required once the core install is completed, except for when updating RVM itself. There is never a reason to use sudo post-install. rvmsudo should only be needed for updating with
$ rvmsudo rvm get head
Important: whenever you upgrade RVM in the future, you should always run rvm notes and rvm requirements as this is usually where you will find details on any major changes and/or additional requirements to ensure your installation stays working.
After the installation, check everything worked with this command:
$ type rvm | head -n1
The response should be:
$ rvm is a function
If you receive rvm: not found, you may need to source your .bash_profile (or wherever you put the line above):
$ . ~/.bash_profile
Check if the rvm function is working:
$ rvm notes
The RVM documentation is quite comprehensive and explanatory. However, here are some RVM usage examples to get you started.
Installing an environment
To see what Ruby environments are available to install, run:
$ rvm list known
To install one, run:
$ rvm install
For example, to install Ruby 1.8.7 one would run the following command:
$ rvm install 1.8.7
This should download, configure and install Ruby 1.8.7 in the place you installed RVM. For example, if you did a single user install, it will be in ~/.rvm/rubies/1.8.7.
To switch from one environment, to another simply run:
$ rvm use
For example to switch to Ruby 1.8.7 one would run the following command:
$ rvm 1.8.7
You should get a message telling you the switch worked. It can be confirmed by running:
$ ruby --version ruby 1.8.7 (2010-01-10 patchlevel 249) [i686-linux]
Note that this environment will only be used in the current shell. You can open another shell and select a different environment for that one in parallel. Also, the default environment will be the system ruby in /usr. This can be changed using RVM if you wish; for more details consult the RVM documentation.
Listing Ruby Environments
To see all installed Ruby environments, run the following command:
$ rvm list
If you've installed a few rubies, this might generate a list like so:
rvm Rubies jruby-1.5.0 [ [i386-java] ] => ruby-1.8.7-p249 [ i386 ] ruby-1.9.2-head [ i386 ] System Ruby system [ i386 ]
The ASCII arrow indicates which environment is currently enabled. In this case, it is Ruby 1.8.7. This could be confirmed by running:
$ ruby --version ruby 1.8.7 (2010-01-10 patchlevel 249) [i686-linux]
$ rvm update
Revert the default ruby to system ruby
If you want to use the system ruby, i.e. the one installed in /usr by the standard Archlinux package, run
$ rvm use system
This is just a simple introduction to switching ruby versions with RVM. There is lots more that you can do with it, including managing different set of gems in different environments. For more information, consult the very comprehensive RVM documentation. This page is a good place to start.
You'll need to take care with rvm installations, since ArchLinux is very well updated, and some earlier ruby's patchlevels do not like it. RVM many times do not choose the latest patchlevel version to install, and you'll need to check manually on the ruby website, and force RVM to install it.
"data definition has no type or storage class"
This appears to be specific to 1.8.7, but if you get this error while compiling the following steps will fix your problem:
$ cd src/ruby-1.8.7-p334/ext/dl $ rm callback.func $ touch callback.func $ ruby mkcallback.rb >> callback.func $ rm cbtable.func $ touch cbtable.func $ ruby mkcbtable.rb >> cbtable.func
Naturally, substitute the actual build path to your source, which will be something like ~/.rvm/src/.
Ruby 1.8.x won't compile with RVM
This is a known issue on Arch Linux, and is caused by a problem with openssl. Arch uses openssl 1.0, lower patchlevels of 1.8.7 assumes 0.9.
Certain patch levels may not build (p352 for example), p299 should work fine and can be installed using the following command:
$ rvm remove 1.8.7 $ rvm install 1.8.7-p299
Another approach is to install local openssl via RVM:
$ rvm pkg install openssl $ rvm remove 1.8.7 $ rvm install 1.8.7 -C --with-openssl-dir=$HOME/.rvm/usr
It may be necessary to patch 1.8.7:
$ wget http://redmine.ruby-lang.org/attachments/download/1931/stdout-rouge-fix.patch $ rvm remove 1.8.7 $ rvm install --patch Downloads/stdout-rouge-fix.patch ruby-1.8.7-p352
Ruby 1.9.1 won't compile with RVM
Like with 1.8.x, earlier patchlevels do not like the OpenSSL 1.0. Then you can use the very same solution above, by installing openssl locally on RVM.
$ rvm pkg install openssl $ rvm remove 1.9.1 $ rvm install 1.9.1 -C --with-openssl-dir=$HOME/./rvm/usr
The patchlevels >p378 have a problem with gem paths, when $GEM_HOME is set. The problem is known and fixed in 1.9.2. (http://redmine.ruby-lang.org/issues/3584). If you really need 1.9.1 please use p378.
$ rvm install 1.9.1-p378 -C --with-openssl-dir=$HOME/./rvm/usr