Skip to main content

Getting RMagic and friends to work on OS-X Mountain Lion

Upgraded my ruby environment today to Mountain Lion.

Here is a quick checklist that I went through to get everything working.  The largest change was having to reinstall XCode and command line tools, and also download XQuarts in order to reinstall ImageMagick successfully. Without it, I was getting errors building RMagick of the following shape:

ld: file not found: /usr/lib/libltdl.7.dylib for architecture x86_64clang:
error: linker command failed with exit code 1
(use -v to see invocation)
make: *** [RMagick2.bundle] Error 1


Quick checklist:
  1. Install Mountain Lion
  2. Install XCode 4.4
  3. Install command line tools from XCode 4.4 Preferences dialog
  4. Install XQuartz
  5. In terminal run
    1. brew update
    2. brew uninstall imagemagick
    3. brew install --fresh imagemagick
    4. wipe out your ~/.rvm folder
    5. reinstall RVM and install the latest ruby 1.9.3-p-194
  6. run "bundle" in the project folder
  7. run "rake" and rejoice

References:

https://github.com/mroth/lolcommits/issues/65

    Comments

    barry said…
    Thanks man! I was about to tack down the creator of rmagick and strangle him! This was much simpler.
    zedtux said…
    You've forgot a "e" in the uninstall line, and you don't need to delete the ~/.rvm folder!!
    Wasim said…
    Thanks alog :)
    Eduludi said…
    brew uninstall imagmagick should be brew uninstall imagemagick
    Adam Bair said…
    You could also try:

    brew install libtool --universal
    brew link libtool --force

    As it might save you a few mins...

    Popular posts from this blog

    Car or Auto Make-Model-Year Database : For Breakfast

    Make Model What?If you like me were tasked with loading a database of recent car makes/models/years, you would start by looking on the web and seeing if someone else just has it out there, readily available, hopefully for free, but perhaps for a tiny nominal fee.?If only it was that simple... I looked and looked, and couldn't find anything that would fit the above requirements. So I thought, who would know about US car models better than Kelly Blue Book? So I went on their site, and sure enough they have a javascript file that lists all known to them makes and models of used cars. Since the file is public, I figured it's not really "evil" if I scrape and parse it for my own benefit. Disagree? Have a better source? Then leave a comment.Anyway, to cut the long story short, I'm hoping to save a day or so to someone else who may, like me, be looking for this information. The ruby module shown below retrieves and parses the javascript from KBB site into a Ruby da…

    Why I Like PostgreSQL

    Today I gave a short presentation at work about PostgreSQL, and why I much prefer it to MySQL.

    PostgreSQL vs MySQL: Eternal Battle
    I may be misreading this, but it seems that there is a recent trend within startups to move away from MySQL, probably thanks to folks like Heroku on one side (who use PostgreSQL to the extreme, and help and contribute to it's development), vs folks like Oracle on the other side, tainting the "open source pureness" of MySQL :)

    At my work we currently use a mid-sized MySQL 5.1 Percona instance, which is holding up quite well I must admit. Both PostgreSQL and MySQL have definitely converged to cover most features that people want, but my leaning is still towards PostgreSQL. I just agree with it's focus on data integrity, recovery, constraints, extensibility, while some of the early decisions in MySQL's design do not agree with me at all (like truncating long strings, 1/0 instead of booleans, ambiguous group by, etc). I think that data …

    On Ruby on Rails with PostgreSQL, and Acts as Paranoid

    Back a few years ago I was researching differences between PostgreSQL and MySQL databases, and chose PostgreSQL because at the time it supported foreign key constraints and many other fantastic SQL extensions that make developer's life a lot easier. Today I am sure MySQL is just as functional as PostgreSQL, and it does appear to be a more popular choice as the Rails DB than MySQL. I still prefer PostgreSQL, it just feels more natural to me coming out of Oracle background, so I am probably biased (who isn't?) Anyway, in the last year and a half or so, I've been writing Rails apps that use PG-based databases and found a few random tricks I'd love to share here. Opinions differ here, but just like accountants like the ancient double entry accounting system, I personally prefer a double validation system - where Rails validates my objects before/after updates, but the database double checks this using proper constraints. Rail's validation system is very robust and ext…