I'm trying to install jruby-9.1.5.0 on macOS Sierra:
$ rbenv install jruby-9.1.5.0
Downloading jruby-bin-9.1.5.0.tar.gz...
-> https://dqw8nmjcqpjn7.cloudfront.net/28e4f3aefbb4497c5c5edc04246778b3305105c3d3d6de11be067826cc5bb766
Installing jruby-9.1.5.0...
BUILD FAILED (OS X 10.12 using ruby-build 20160913)
Inspect or clean up the working tree at /var/folders/r2/6pxx62xx727c7_h4qp6zrpxw0000gn/T/ruby-build.20160928184430.30804
Results logged to /var/folders/r2/6pxx62xx727c7_h4qp6zrpxw0000gn/T/ruby-build.20160928184430.30804.log
Here is the log file:
/var/folders/r2/6pxx62xx727c7_h4qp6zrpxw0000gn/T/ruby-build.20160928184430.30804 ~
HTTP/1.1 200 OK
Content-Type: binary/octet-stream
Content-Length: 31874967
Connection: keep-alive
Date: Wed, 28 Sep 2016 15:42:45 GMT
Last-Modified: Wed, 07 Sep 2016 07:00:45 GMT
ETag: "e9b2cc44757db4cfbe7da79601d0169a"
Accept-Ranges: bytes
Server: AmazonS3
Age: 108
X-Cache: Hit from cloudfront
Via: 1.1 034e630e8674ac0b9c29358c6c3163d4.cloudfront.net (CloudFront)
X-Amz-Cf-Id: 6IQvB6FZ3piQ7EmMsm6Kcl1cSc91WYKdWQXGhgZL2SXrU6wVkcBOjg==
/var/folders/r2/6pxx62xx727c7_h4qp6zrpxw0000gn/T/ruby-build.20160928184430.30804/jruby-9.1.5.0 /var/folders/r2/6pxx62xx727c7_h4qp6zrpxw0000gn/T/ruby-build.20160928184430.30804 ~
ERROR: While executing gem ... (IOError)
No route to host
Any suggestions?
Closing. Not reproducing anymore.
(after reboot LOL)
In case anyone falls over this again (as i did).
We had (still have..) the same issue here. But only from select internet connections (our office).
Possible workarounds:
I had the same issue when using a mobile hotspot provided by iPhones over Verizon. Adding Google as my DNS server resolved.
Thanks very much @maxigs God bless you!! I was installing RVM with jruby, rails and puma and faced this error. So, as you instructed, I pointed my DNS to Google and the error gone away.
I had the same issue when using a mobile hotspot provided by iPhones over Verizon. Adding Google as my DNS server resolved.
This works for me. Tks
Switching the DNS to google solved it.
https://developers.google.com/speed/public-dns/docs/using
Most helpful comment
In case anyone falls over this again (as i did).
We had (still have..) the same issue here. But only from select internet connections (our office).
Possible workarounds: