Recent problems with rbenv
$ rbenv -v rbenv 1.1.2-34-g0843745 If there is no update from August 2nd to 10th, everything seems to be this version
What happened during trial and error on old Mac OS X.
Anything will do as long as it can be downloaded. However
Here's what happened with Mac OS X El Capitan 10.11. 4. Even if openssl 1.1.1g is already installed and the path is in place, install it separately under .rbenv. 5. The download is successful with rbenv install 2.5.8. This time, with ruby 2.0.0 $ ruby -ropenssl -e "p OpenSSL::X509::DEFAULT_CERT_FILE" "/System/Library/OpenSSL/cert.pem" As it is 1.1.1g of / usr / local / bin / openssl (although not used) 7.71.1 in / usr / local / bin / curl What does it mean to succeed with this combination? It seems that you are communicating with curl, but wget? Are you using old curl?
curl7.30.0
$ /usr/bin/curl --version
curl 7.30.0 (x86_64-apple-darwin13.0) libcurl/7.30.0 SecureTransport zlib/1.2.5
Protocols: dict file ftp ftps gopher http https imap imaps ldap ldaps pop3 pop3s rtsp smtp smtps telnet tftp
Features: AsynchDNS GSS-Negotiate IPv6 Largefile NTLM NTLM_WB SSL libz
6, This is a user problem,
export PATH="
Execute the following command.
$ echo "
Reference 1. May be important (2015 article) How does rbenv + ruby-build work --takatoshiono's blog
The directories are very different between homebrew and rbenv. Originally, there should be no problem with multiple directories by specifying the prefix and linking after installation, but isn't homebrew and rbenv all crazy?
Conclusion Unless the above problem is solved, I think that it is best to build ruby source and switch the path without using rbenv for the time being.
Reference 2 What is rbenv doing? --The crayfish was watching ...