From: shibata.hiroshi@...
Date: 2014-09-15T00:45:45+00:00
Subject: [ruby-core:65042] [ruby-trunk - Bug #10235] [Rejected] make fails to configure OpenSSL on OS X 10.9.4 (Mavericks)

Issue #10235 has been updated by Hiroshi SHIBATA.

Status changed from Open to Rejected

----------------------------------------
Bug #10235: make fails to configure OpenSSL on OS X 10.9.4 (Mavericks)
https://bugs.ruby-lang.org/issues/10235#change-48911

* Author: opt1c -
* Status: Rejected
* Priority: Normal
* Assignee: 
* Category: 
* Target version: 
* ruby -v: 2.1.2, 2.1.0
* Backport: 2.0.0: UNKNOWN, 2.1: UNKNOWN
----------------------------------------
"Failed to configure openssl. It will not be installed."

OPENSSL
-------

$ which openssl
/usr/local/ssl/bin/openssl
$ openssl version
OpenSSL 1.0.1i 6 Aug 2014

As recommended by: https://www.ruby-lang.org/en/news/2014/04/10/severe-openssl-vulnerability/

When installed, OpenSSL was configured with: ./Configure darwin64-x86_64-cc. It works fine.

RUBY
----

I've tried both:

./configure --prefix=/Users/me/.rbenv/versions/2.1.2 --with-openssl-dir=/usr/local/ssl
./configure --prefix=/Users/me/.rbenv/versions/2.1.2 --with-openssl-dir=/usr/local/ssl --with-gcc=clang --enable-shared --enable-pthread CFLAGS=-D_XOPEN_SOURCE=1

(As well as attempts including "--with-opt-dir=/usr/local/ssl" which I believe was required of an older Ruby.)

ruby-2.1.2/ext/openssl:$ ruby extconf.rb
  checking for t_open() in -lnsl... no
  checking for socket() in -lsocket... no
  checking for assert.h... yes
  checking for openssl/ssl.h... yes
  checking for OpenSSL_add_all_digests() in -lcrypto... no
  checking for OpenSSL_add_all_digests() in -llibeay32... no

So errors include:

  conftest.c:13:57: error: use of undeclared identifier 't_open'
  conftest.c:13:57: error: use of undeclared identifier 'socket'
  conftest.c:13:57: error: use of undeclared identifier 'OpenSSL_add_all_digests'

I use rbenv and install from source, but I've also since tried rbenv with the ruby-build plugin and it fails, too (as would be expected, based on the above, but it was attempted, anyway).



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