Skip to content

Instantly share code, notes, and snippets.

@sayems
Created January 23, 2013 01:13
Show Gist options
  • Select an option

  • Save sayems/4600744 to your computer and use it in GitHub Desktop.

Select an option

Save sayems/4600744 to your computer and use it in GitHub Desktop.
# When Mac OS X Mountain Lion was released, I did a completely clean install. Unfortunately [RVM](http://rvm.io) won't install directly on the stock release. Here are the steps to get the installation working.
# This gist is based in part by [this post](http://theengguy.blogspot.ca/2012/04/setting-up-os-x-lion-and-mountain-lion.html) by [@theengguy](http://twitter.com/theengguy).
# 1. Install [MacPorts](http://www.macports.org)
# You can snag the package installer (easiest) from [https://distfiles.macports.org/MacPorts/MacPorts-2.1.2-10.8-MountainLion.pkg](https://distfiles.macports.org/MacPorts/MacPorts-2.1.2-10.8-MountainLion.pkg)
# 2. Install a new version of curl
sudo port -v selfupdate
sudo port install curl
# This will install another, more up to date version of curl to /opt/local/bin/curl. Mountain Lion ships with 7.25.0 and you need at least 7.26.0 in order to avoid libcurl error, "(48) An unknown option was passed in to libcurl" while trying to install RVM
# 3. Check the curl version and make it active
/opt/local/bin/curl -V
# Make sure the output is >= 7.26.0
# 3. Install RVM by running the following commands from [@theengguy](http://twitter.com/theengguy);
sudo port -v selfupdate
sudo port install apple-gcc42
sudo port install gmake
sudo port install gpatch
sudo ln -s /opt/local/bin/gcc-apple-4.2 /opt/local/bin/gcc
sudo ln -s /opt/local/bin/gmake /opt/local/bin/make
sudo ln -s /opt/local/bin/gpatch /opt/local/bin/patch
curl -L get.rvm.io | bash -s stable
source ~/.rvm/scripts/'rvm'
export PATH=/opt/local/bin:$PATH
rvm install 1.9.3
rvm use 1.9.3@rails3tutorial2ndEd --create --default
gem update --system 1.9.3
rvm use 1.9.3
# You should have a working installation of RVM with Ruby 1.9.2 installed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment