From: SASADA Koichi <ko1@...>
Date: 2014-01-30T21:20:25+09:00
Subject: [ruby-core:60342] Re: Building ext/openssl outside of trunk

We can expose this header file.

I didn't expose these interface because I didn't want to consider
function names (and parameters) seriously. It is an issue everytime :(


(2014/01/28 9:41), Martin Bo�let wrote:
> If I remember correctly, @ko1 had to use this as a consequence
> of https://bugs.ruby-lang.org/issues/8386. I guess a workaround would be
> to revert to the previous state, but this would also mean breaking
> thread-safety in Rubinius.
> 
> -Martin
> 
> 
> 2014-01-24 Aaron Patterson <tenderlove@ruby-lang.org
> <mailto:tenderlove@ruby-lang.org>>
> 
>     Hi,
> 
>     It looks like it's not possible to build ext/openssl outside of ruby
>     itself because ossl.c includes thread_native.h:
> 
>      
>     https://github.com/ruby/ruby/blob/8cacc6459067340d5ce76e017d0891162c0f31ef/ext/openssl/ossl.c#L469-L480
> 
>     @ko1, @emboss is there a way to do this without relying on Ruby
>     internals?
> 
>     Thanks!
> 
>     --
>     Aaron Patterson
>     http://tenderlovemaking.com/
> 
> 


-- 
// SASADA Koichi at atdot dot net