Issue #6830 has been updated by luislavena (Luis Lavena).


=begin
Hello guys,

If I can chime in, something similar happens on Windows:

https://github.com/oneclick/rubyinstaller/pull/120#issuecomment-6641054

And we workaround the issue by setting (({OPENSSL_CONF})) environment variable.

Now, I believe the root issue is not OpenSSL extension but OpenSSL itself that is using hardcoded paths.

At least Ruby tests should check if the default configuration file exists prior attempting to load it, as suggested in the RubyInstaller comment.

This issue is very common on Windows, where packages/libraries can be relocated to different drives or paths altogether, turning hardcoded paths into a problem.
=end

----------------------------------------
Bug #6830: test failure test_constants(OpenSSL::TestConfig) [/ruby/test/openssl/test_config.rb:27] on Mac + homebrew
https://bugs.ruby-lang.org/issues/6830#change-28639

Author: kosaki (Motohiro KOSAKI)
Status: Assigned
Priority: Normal
Assignee: MartinBosslet (Martin Bosslet)
Category: ext
Target version: 2.0.0
ruby -v: ruby 2.0.0dev (2012-08-04 trunk 36617) [x86_64-darwin12.0.0]


When using homebrew openssl, following test failure was happen.

  2) Failure:
test_constants(OpenSSL::TestConfig) [/Users/kosaki/ruby/git/test/openssl/test_config.rb:27]:
Exception raised:
<#<Errno::ENOENT: No such file or directory - /usr/local/openssl-1.0.1c/openssl.cnf>>.

rough analysis.

homebrew installed openssl library to "/usr/local/Cellar/openssl/1.0.1c". 

and following program output "/usr/local/openssl-1.0.1c".

--------------------------
int main()
{
  printf("%s\n",	X509_get_default_cert_area());
  return 0;
}
--------------------------


I'm using following configure options.

configure \
?? ?? --disable-install-doc \
?? ?? --with-baseruby=/usr/bin/ruby \
?? ?? --prefix=${HOME}/local/ruby-${suffix} \
?? ?? --program-suffix=-${suffix} \
    --with-openssl-dir=/usr/local/Cellar/openssl/1.0.1c


So, I have several questions.

1) Is X509_get_default_cert_area() a right way to obtain configuration file?
2) If yes, is this homebrew bug?
3) if yes, should we skip this test when using Mac OS X?




-- 
http://bugs.ruby-lang.org/