Compiling Ruby 2.0, problem with OpenSSL

Trying to compile Ruby 2.0 from source, having problem with it, getting
an error regarding OpenSSL, installed the newest version also from
source. What can I do?

Attachments:
http://www.ruby-forum.com/attachment/8204/screen.jpg

···

--
Posted via http://www.ruby-forum.com/.

Could you please file that as a bug on bugs.ruby-lang.org and assign it to
me (Martin Boßlet)? Thanks!

In the meantime, it should work if you choose to install OpenSSL 1.0.1c.
There's conflicting declarations in 1.0.1e for methods that didn't exist
yet in previous versions.

-Martin

···

2013/3/7 Piotr P. <lists@ruby-forum.com>

Trying to compile Ruby 2.0 from source, having problem with it, getting
an error regarding OpenSSL, installed the newest version also from
source. What can I do?

Attachments:
http://www.ruby-forum.com/attachment/8204/screen.jpg

--
Posted via http://www.ruby-forum.com/\.

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/.

"Martin Boßlet" <martin.bosslet@gmail.com> wrote in post #1100624:

Could you please file that as a bug on bugs.ruby-lang.org and assign it
to
me (Martin Bolet)? Thanks!

In the meantime, it should work if you choose to install OpenSSL 1.0.1c.
There's conflicting declarations in 1.0.1e for methods that didn't exist
yet in previous versions.

-Martin

That did not help. See attached image.

Attachments:
http://www.ruby-forum.com/attachment/8206/Screen_Shot_2013-03-08_at_8.57.21_AM.png

···

2013/3/7 Piotr P. <lists@ruby-forum.com>

--
Posted via http://www.ruby-forum.com/\.

"Martin Boßlet" <martin.bosslet@gmail.com> wrote in post #1100624:

Could you please file that as a bug on bugs.ruby-lang.org and assign it
to
me (Martin Bolet)? Thanks!

In the meantime, it should work if you choose to install OpenSSL 1.0.1c.
There's conflicting declarations in 1.0.1e for methods that didn't exist
yet in previous versions.

-Martin

Or maybe I am compiling it wrong?

./configure --prefix=/usr/ darwin64-x86_64-cc
make
sudo make install

···

2013/3/7 Piotr P. <lists@ruby-forum.com>

--
Posted via http://www.ruby-forum.com/\.

Hi there,

···

On 07.03.2013, at 23:55, Martin Boßlet <martin.bosslet@gmail.com> wrote:

In the meantime, it should work if you choose to install OpenSSL 1.0.1c. There's conflicting declarations in 1.0.1e for methods that didn't exist yet in previous versions.

I compiled openssl 1.0.1e and ruby 2.0 on my machine and did not notice any errors. See the "Mac OS 10.8.2 and openssl" thread.

Cheers,
-- Jan

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. <lists@ruby-forum.com>

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/\.

How do I unsubscribe from this mailing list? Thanks

···

Sent from my iPhone

On Mar 7, 2013, at 5:55 PM, Martin Boßlet <martin.bosslet@gmail.com> wrote:

Could you please file that as a bug on bugs.ruby-lang.org and assign it to me (Martin Boßlet)? Thanks!

In the meantime, it should work if you choose to install OpenSSL 1.0.1c. There's conflicting declarations in 1.0.1e for methods that didn't exist yet in previous versions.

-Martin

2013/3/7 Piotr P. <lists@ruby-forum.com>

Trying to compile Ruby 2.0 from source, having problem with it, getting
an error regarding OpenSSL, installed the newest version also from
source. What can I do?

Attachments:
http://www.ruby-forum.com/attachment/8204/screen.jpg

--
Posted via http://www.ruby-forum.com/\.

Send
# bye
or
# unsubscribe
to ruby-talk-ctl@ruby-lang.org.

···

2013/3/8, Adam Todd <adamtodd@yahoo.com>:

How do I unsubscribe from this mailing list? Thanks

Sent from my iPhone

On Mar 7, 2013, at 5:55 PM, Martin Boßlet <martin.bosslet@gmail.com> wrote:

Could you please file that as a bug on bugs.ruby-lang.org and assign it to
me (Martin Boßlet)? Thanks!

In the meantime, it should work if you choose to install OpenSSL 1.0.1c.
There's conflicting declarations in 1.0.1e for methods that didn't exist
yet in previous versions.

-Martin

2013/3/7 Piotr P. <lists@ruby-forum.com>

Trying to compile Ruby 2.0 from source, having problem with it, getting
an error regarding OpenSSL, installed the newest version also from
source. What can I do?

Attachments:
http://www.ruby-forum.com/attachment/8204/screen.jpg

--
Posted via http://www.ruby-forum.com/\.

"Martin Boßlet" <martin.bosslet@gmail.com> wrote in post #1100727:

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

Yes, go ahead.

···

2013/3/8 Piotr P. <lists@ruby-forum.com>

--
Posted via http://www.ruby-forum.com/\.

Hi,

I have (what appears to be) a very similar problem, should I open a new
issue or use the old one? (for which I'd need the reference)

Regards,
Iain

···

On 11 March 2013 12:46, Piotr P. <lists@ruby-forum.com> wrote:

"Martin Boßlet" <martin.bosslet@gmail.com> wrote in post #1100727:
> 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. <lists@ruby-forum.com>

Yes, go ahead.

--
Posted via http://www.ruby-forum.com/\.