Hampton Lintorn Catlin

ginstall with gems

So, I don’t know what changed. Apparently some ruby gems have a fancy new way of building themselves and it gives this lovely complaint on Snow Leopard:

make install
        /opt/local/bin/ginstall -c -m 0755 nokogiri.bundle /usr/local/lib/ruby/gems/1.8/gems/nokogiri-1.4.0/lib/nokogiri
        make: /opt/local/bin/ginstall: No such file or directory
        make: *** [/usr/local/lib/ruby/gems/1.8/gems/nokogiri-1.4.0/lib/nokogiri/nokogiri.bundle] Error 1

Oh man.

BUT, I FIGURED IT OUT. So, after a crap load of Googling… ginstall is the same thing as install. Thusly this should solve your problem.

sudo ln -s /usr/bin/install /opt/local/bin/ginstall



Dec 3, 2009
Mark Carey said...
It looks like it's expecting the coreutils port to be installed: sudo port install coreutils
Feb 27, 2010
Andre said...
Hey thanks a lo to you both. I was wondering why I was getting loads of errors when trying to install ruby 1.9+ gems.
Apr 14, 2010
Thibaut said...
thank you so much :) I've been looking for this for quite a long time.
Aug 19, 2010
dissolved said...
This is crazy! I mean, thank you... this got me going again... but are gems really now expecting MacPorts to be installed?!? This problem crept up for me after uninstalling MacPorts and installing Homebrew.
Mar 28, 2011
Xiao Li said...
Thank you, it works.