pagj2w
Last Updated: February 25, 2016
·
13.54K
· phlipper
B61ce134adf2d6eb1d1f1d11122d6142

Upgrading to Mountain Lion - Ruby + MacPorts

My colleague Kenny Johnston wrote a nice piece about Upgrading to Mountain Lion with an emphasis on using Homebrew. Here are the relevant steps using MacPorts:

XCode:

  • Update to the latest XCode 4.4 from the App Store
  • Install the Command Line Tools

Of course, since it is zero-day, there was an issue fetching the Command Line Tools from the server and I had to install manually from a .pkg file retrieved from the Apple Developer Portal. If you install the CLI tools package manually, you may need to run the following:

sudo xcodebuild -license

That is required to accept the license terms system-wide.

MacPorts

First, you'll need to update the base MacPorts installation:

sudo port -v selfupdate

If you run in to a compilation error, you may need to edit the file /opt/local/etc/macports/macports.conf and set the developer_dir option to be empty:

sudo vim /opt/local/etc/macports/macports.conf

# Directory containing Xcode Tools (default is to ask xcode-select)
#developer_dir       /Developer
developer_dir

You should now be able to update any outdated ports (grab a beverage while you wait):

sudo port -vu upgrade outdated

GCC 4.2

Now install the apple-gcc42 port to replace the missing GCC 4.2 in Mountain Lion:

sudo port install -vu apple-gcc42

Once that has been installed, you will need to link it to the expected system location:

sudo ln -s /opt/local/bin/gcc-apple-4.2 /usr/bin/gcc-4.2

RVM

Make sure you have the latest RVM version installed:

curl -L https://get.rvm.io | bash -s stable

You should now ensure that you can rebuild your installed Ruby versions:

rvm reinstall 1.9.3
rvm reinstall rbx
...

You may need to reference my earlier tip: Fix Ruby 1.9.x OpenSSL Segfault on OS X

3 Responses
Add your response

2680

Y U NO use homebrew ?

over 1 year ago ·
2713
B61ce134adf2d6eb1d1f1d11122d6142

@happynoff, MacPorts works, well and reliably. It also supports a lot of functionality which I use that homebrew doesn't support (activating/deactivating multiple versions for testing libraries, for example). Homebrew is great, and I recommend it often for many folks, but I need a better reason than "everyone else is doing it" to make the move myself.

Thanks for the input!

over 1 year ago ·
2759

I see :) good to know why people may stick to macports ;)

over 1 year ago ·