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

ASF GitHub Bot commented on IGNITE-8626:
----------------------------------------

GitHub user isapego opened a pull request:

    https://github.com/apache/ignite/pull/5590

    IGNITE-8626: ODBC and C++ thin now support OpenSSL 1.1

    

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

    $ git pull https://github.com/gridgain/apache-ignite ignite-8626

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

    https://github.com/apache/ignite/pull/5590.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 #5590
    
----
commit b920442b2e3a68376bf48de4bcc98c98183ae2f5
Author: Igor Sapego <isapego@...>
Date:   2018-12-04T17:25:34Z

    IGNITE-8626: Added OpenSSL 1.1 support for Windows

commit 985c3261ed9c9554100014fbfaf5ad855edae7b5
Author: Igor Sapego <isapego@...>
Date:   2018-12-04T18:52:38Z

    IGNITE-8626: Implemented for ODBC

commit 872cfa855e1adfd2b44162d9be8ae63837301742
Author: Igor Sapego <isapego@...>
Date:   2018-12-05T11:28:01Z

    IGNITE-8626: Fix for OpenSSL 1.0

commit 609cc826cfcb433ef6f59d3508dceccefa36e096
Author: Igor Sapego <isapego@...>
Date:   2018-12-05T15:45:54Z

    IGNITE-8626: Fixes for Linux build system

----


> CPP: Can not compile ODBC and thin client with OpenSSL 1.1
> ----------------------------------------------------------
>
>                 Key: IGNITE-8626
>                 URL: https://issues.apache.org/jira/browse/IGNITE-8626
>             Project: Ignite
>          Issue Type: Bug
>          Components: odbc, thin client
>    Affects Versions: 2.4
>            Reporter: Igor Sapego
>            Assignee: Igor Sapego
>            Priority: Major
>             Fix For: 2.8
>
>         Attachments: 01(1).patch
>
>
> Can not compile ODBC and thin client with OpenSSL 1.1.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to