Youri van der Lans

@bendangelo Any chance of this getting merged :)?

Ok, I can probably answer my own question 😅 This seems to work: ```jsx Hello World! ``` Leaving this here for anyone else searching for this.

Would you happend to remember what arguments you used to compile the package? From what I understand you should use the same Ruby version as the compiler does. Also, when...

I'd suggest you use [RVM](https://rvm.io/) or [rbenv](https://github.com/rbenv/rbenv) to be able to have multiple ruby versions installed. This way you don't have to worry about the ruby version installed on the...

I see, a `Gemfile` with your dependencies should be picked up by the compiler and be put in the package so it can be used by your program.

Probably the compiled package cannot use the certificates on the system and it doesn't have any included. You could use something like this gem https://github.com/liveeditor/net_http_ssl_fix to fix the issue.

@andy-twosticks I fully agree, its not ideal. Compiled programs not using https will probably run fine. I assume the developers hadn't seen this edge case before. Last resort could also...

This is my output: ``` $ ruby -e "require 'openssl'; puts OpenSSL::X509::DEFAULT_CERT_FILE" /usr/local/etc/openssl/cert.pem $ ENCLOSE_IO_ALWAYS_USE_ORIGINAL_RUBY=1 ENCLOSE_IO_USE_ORIGINAL_RUBY=1 ./a.out -e "require 'openssl'; puts OpenSSL::X509::DEFAULT_CERT_FILE" /usr/local/ssl/cert.pem ```

I've done a bit of testing and come to the following conclusions: 1. Using 0.4.0 building openssl with `--openssldir=/usr/local/etc/openssl` will ensure the build succeeds (so gems from https sources get...

That would be ok for people wanting to compile a package. But then when the package gets distributed and other systems don't have the certifications in `/usr/local/etc/openssl` the program will...