I checked gem: $ which gem /usr/bin/gem
Seems to be Apple's installed gem. I wanted to add an alias to .bash_profile for it and did so. All of the sudden all my command line commands such as mate and port would no longer work. I had to deactivate .bash_profile, .bash_login and .bash_history. After .bash_history regenerated itself again I reinstated .bash_profile and was able to use mate and port and so on again. So I was able to add the alias for gem. But then all of the sudden the mate command no longer works so I have to deactivate .bash_profile again... Odd again. On Sun, Jun 10, 2012 at 10:43 AM, Jeremy Lavergne < [email protected]> wrote: > > I don't get it.. > > The big take away is gem is probably the wrong one, either an alias needs > set or you need to use the full path when you call it. Since the version of > gem changed, likely all the ruby gems need rebuilt (not a rubyist, so not > actually certain here). Make sure the commands you're running match up with > the ones you meant to run, and of course that you still have installed the > versions you're expecting as well. > > Libffi probably is because libffi was updated and it broke ABI > compatibility. Since we don't keep a mapping of what version of each > library a given package uses... when you come across that sort of an error > let MacPorts devs know and we'll force a rebuilt of whatever failed to load > libffi. > >
_______________________________________________ macports-users mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
