[ 
https://issues.apache.org/jira/browse/THRIFT-3878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15533733#comment-15533733
 ] 

ASF GitHub Bot commented on THRIFT-3878:
----------------------------------------

GitHub user jeking3 opened a pull request:

    https://github.com/apache/thrift/pull/1102

    THRIFT-3878: fix interop with newer OpenSSL libraries

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/jeking3/thrift defect/THRIFT-3878

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/thrift/pull/1102.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1102
    
----
commit cc4f32db13ddc62fbd1e316127c5a60f4080a2d3
Author: James E. King, III <[email protected]>
Date:   2016-09-29T19:04:09Z

    THRIFT-3878: fix interop with newer OpenSSL libraries

----


> Compile error in TSSLSocket.cpp
> -------------------------------
>
>                 Key: THRIFT-3878
>                 URL: https://issues.apache.org/jira/browse/THRIFT-3878
>             Project: Thrift
>          Issue Type: Bug
>          Components: C++ - Library
>    Affects Versions: 1.0
>         Environment: VS2013
> Thrift from git repo, SHA-1: 5a3f855b4e6882184f13c698855c877241144a12 (master)
> OpenSSL from git repo (master).
>            Reporter: Sergey Fasman
>            Assignee: James E. King, III
>            Priority: Trivial
>
> In TSSLSocket if use new OpenSSL library (downloaded and builded from git) 
> will be compile error.
> That because CRYPTO_num_locks is now macro-call instead of function.
> THRIFT -also from git repo (master).
> So I simply fix that:
> #ifdef CRYPTO_num_locks
>   mutexes = boost::shared_array<Mutex>(new Mutex[CRYPTO_num_locks()]);
> #else
>   mutexes = boost::shared_array<Mutex>(new Mutex[ ::CRYPTO_num_locks()]);
> #endif



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to