Mac OS 10.8.2 and openssl

Ruby
21

On Wed, Feb 27, 2013 at 4:21 PM, Hassan S.
[email protected] wrote:

On Wed, Feb 27, 2013 at 2:55 PM, Jeremy K. [email protected] wrote:

10.7.x does not have this issue.

So what exactly is the issue, if not the version of OpenSSL?

10.8.x ships a patched OpenSSL that Ruby won’t compile with.

22

Subject: Re: Mac OS 10.8.2 and openssl
Date: gio 28 feb 13 05:09:24 +0900

Quoting Dr. Hegewald ([email protected]):

? Also, the contents of the mkmf.log file may be useful.

This is the openssl/mkmf.log:

Ignore OpenSSL broken by Apple.
Please use another openssl. (e.g. using `configure
–with-openssl-dir=/path/to/openssl’)
Failed to configure openssl. It will not be installed.

Only? If so, your ruby source must be damaged. There should be a lot of
other stuff in the file.

Try to execute this short script, AFTER SETTING PKG_CONFIG_PATH as I
wrote yesterday:

–8<----8<----8<----8<----8<----8<----8<----8<----8<–
require ‘mkmf’
p pkg_config(‘openssl’)
p
have_func(‘SSL_library_init()’,‘openssl/ssl.h’,’-Werror=deprecated-declarations’)
p have_header(‘openssl/ssl.h’,nil,’-Werror=deprecated-declarations’)
–8<----8<----8<----8<----8<----8<----8<----8<----8<–

What is the output, and what is the entire content of the resulting
mkmf.log? (Note that my file is 50 lines long).

The point is that, after executing pkg_config, you should only access
your new copy of openssl, which should pass that test. At least this
is what happens here.

Carlo

23

Hey, I have a radical and crazy idea.

How about, instead of having every single person who wants to install
ruby and gems on OSX have to jump through this stupid series of
ridiculous hoops, the relatively few ruby DEVELOPERS actually fix the
build configuration (for OS X and others as well)? The man-hours spent
this way are all upside down. Fix it at the head, not at the tail. This
kind of hopeless head-banging by all of us is an idiotic expectation.

The fact that “–with-openssl-dir” apparently throws meaningless errors
(or are they meaningful, and how the hell are we supposed to know?)
proves that ruby devs aren’t minding the store.

Someone(s) who understand(s) the “configure” and “automake” setup
should actually provide documentation for --with-openssl-dir and
–with-out-tcl and --with-out-tk and the dozens of other parameters that
cause lots of errors that the build plows right through. Use these
parameters at all and have the system bark at you. And expect them to
have no effect as well, in my experience.

A ruby USER shouldn’t have to know everything that the ruby DEVS do, but
we are getting closer to it with every release. This is only one more
thing to really make it a pain in the neck for every OSX ruby user out
here. It almost feels like ruby devs want to make ruby such a pain to
build or install that the rest of us will give up on it.

Better yet, Apple, how about releasing ruby 2.0 with your next iteration
of OS X? OK, now I’m obviously hallucinating.