From: "Martin Boßlet" Date: 2013-03-09T01:55:24+09:00 Subject: Re: Compiling Ruby 2.0, problem with OpenSSL --f46d043c811e5dd66504d76c9788 Content-Type: text/plain; charset=ISO-8859-1 I wanted to mention that, that using --with-openssl-dir could be important. I'm still struggling to reproduce your error, though. I thought it would be about 1.0.1e, but as Dr. Hegewald and I independently confirmed, it's not. Really strange, I wonder what has caused this conflict... Is it OK if I close the issue on Redmine then? -Martin 2013/3/8 Piotr P. > Managed to solve the problem with compiling openssl like this: > > sudo ./configure --with-openssl-dir=/usr/local/ > > and not this: > > sudo ./configure --with-openssl-dir=/usr/ > > Also my /etc/paths now look like this: > > /usr/local/bin > /usr/local/bin > /usr/bin > /bin > /usr/sbin > /sbin > > Compiled Ruby 2.0 with this: > > sudo ./configure --with-openssl-dir=/usr/local/ > > -- > Posted via http://www.ruby-forum.com/. > > --f46d043c811e5dd66504d76c9788 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
I wanted to mention that, that using --with-openssl-dir co= uld be important. I'm still struggling to reproduce your error, though.= I thought it would be about 1.0.1e, but as Dr. Hegewald and I independentl= y confirmed, it's not. Really strange, I wonder what has caused this co= nflict...

Is it OK if I close the issue on Redmine then?

-Martin


2013/3/8 Piotr P. <= ;lists@ruby-forum= .com>
Managed to solve the problem with compiling = openssl like this:

sudo ./configure --with-openssl-dir=3D/usr/local/

and not this:

sudo ./configure --with-openssl-dir=3D/usr/

Also my /etc/paths now look like this:

/usr/local/bin
/usr/local/bin
/usr/bin
/bin
/usr/sbin
/sbin

Compiled Ruby 2.0 with this:

sudo ./configure --with-openssl-dir=3D/usr/local/

--f46d043c811e5dd66504d76c9788--