Fresh RVM and Ruby 2.1.1 installations - dyld library / path error

I'm trying to install RVM and Ruby 2.1.1 on a new Mac (OS 10.9.2) and everything seems to be going fine until I try to install any version of Ruby.

My input

$ rvm reinstall 2.1 

So far so good ...

 ruby-2.1.1 - #removing rubies/ruby-2.1.1.. Searching for binary rubies, this might take some time. Found remote file https://rvm.io/binaries/osx/10.9/x86_64/ruby-2.1.1.tar.bz2 Checking requirements for osx. Certificates in '/usr/local/etc/openssl/cert.pem' already are up to date. Requirements installation successful. ruby-2.1.1 - #configure ruby-2.1.1 - #download ruby-2.1.1 - #validate archive ruby-2.1.1 - #extract ruby-2.1.1 - #validate binary ruby-2.1.1 - #setup ruby-2.1.1 - #making binaries executable.. ruby-2.1.1 - #downloading rubygems-2.2.2 ruby-2.1.1 - #extracting rubygems-2.2.2.... ruby-2.1.1 - #removing old rubygems......... 

But then...

 ruby-2.1.1 - #installing rubygems-2.2.2. Error running 'env GEM_HOME= GEM_PATH= /Users/dylanoshea/.rvm/rubies/ruby-2.1.1/bin/ruby -d /Users/dylanoshea/.rvm/src/rubygems-2.2.2/setup.rb --verbose', showing last 15 lines of /Users/dylanoshea/.rvm/log/1395654507_ruby-2.1.1/rubygems.install.log [2014-03-24 02:48:47] /Users/dylanoshea/.rvm/rubies/ruby-2.1.1/bin/ruby current path: /Users/dylanoshea/.rvm/src/rubygems-2.2.2 PATH=/usr/local/opt/pkg-config/bin:/usr/local/opt/libtool/bin:/usr/local/opt/automake/bin:/usr/local/opt/autoconf/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/Users/dylanoshea/.rvm/bin command(7): env GEM_HOME= GEM_PATH= /Users/dylanoshea/.rvm/rubies/ruby-2.1.1/bin/ruby -d /Users/dylanoshea/.rvm/src/rubygems-2.2.2/setup.rb --verbose dyld: Library not loaded: /Users/mpapis/.sm/pkg/versions/openssl/1.0.1f/lib/libssl.1.0.0.dylib Referenced from: /Users/dylanoshea/.rvm/rubies/ruby-2.1.1/bin/ruby Reason: image not found /Users/dylanoshea/.rvm/scripts/functions/support: line 411: 14265 Trace/BPT trap: 5 "$ruby_path" -rrbconfig -e '\ File.open("'"$config_path"'","w") { |file| RbConfig::CONFIG.sort.each{|key,value| file.write("#{key.gsub(/\.|-/,"_")}=\"#{value.gsub("$","\\$")}\"\n") } } ' > /dev/null 2>&1 dyld: Library not loaded: /Users/mpapis/.sm/pkg/versions/openssl/1.0.1f/lib/libssl.1.0.0.dylib Referenced from: /Users/dylanoshea/.rvm/rubies/ruby-2.1.1/bin/ruby Reason: image not found Empty path passed to certificates update, functions stack: requirements_osx_update_openssl_cert_run rvm_requiremnts_fail_or_run_action __rvm_osx_ssl_certs_ensure_for_ruby __rvm_osx_ssl_certs_ensure_for_ruby_except_jruby external_import_setup external_import main Gemset '' does not exist, 'rvm ruby-2.1.1 do rvm gemset create ' first, or append '--create'. __rvm_rm_rf already gone: /Users/dylanoshea/.rvm/tmp/5021* 

I have repeatedly tried uninstalling, untying, uninstalling and reinstalling all my RVM components and Ruby versions, but that does not matter - I still get this error. Curiously, the broken path refers to "mpapis", which is one of the developers of RVM.

dyld: Library not loaded: /Users/ mpapis /.sm/pkg/versions/openssl/1.0.1f/lib/libssl.1.0.0.dylib

Any help?

+44
ruby rubygems rvm dyld
Mar 24 '14 at 9:52
source share
2 answers

It looks like a temporary error: https://twitter.com/mpapis/status/447926386314186752 . The disable-binary option worked for me:

 rvm reinstall 2.1.1 --disable-binary 

EDIT is the best solution

I see some people have this kind of problem. Today, a much better solution is to upgrade the RVM as follows:

 rvm get stable 

The problem was caused by RVM - it had some hard-coded paths into binary versions of ruby. But this problem has already been fixed, and there is currently no need to compile the ruby ​​in place. All you need to do is get the latest version of RVM.

+92
Mar 24 '14 at 11:01
source share

according to https://github.com/wayneeseguin/rvm/issues/2732 :

rvm reinstall 2.1.1 --disable-binary

should let you install it.

also helped me tune "use rvm" to the latest ruby ​​in your "rvm list".

and the problem is now closed on github, so in a couple of days (the question is: does anyone know the usual turn for rvm patches?), the fix should be on the rvm.io website and running β€œrvm get stable” will update your patch installation

+4
Mar 25 '14 at 16:55
source share



All Articles