You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@thrift.apache.org by "Roger Meier (JIRA)" <ji...@apache.org> on 2016/01/18 00:11:39 UTC

[jira] [Commented] (THRIFT-3555) 'configure' script does not honor --with-openssl= for libcrypto for BN_init

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

Roger Meier commented on THRIFT-3555:
-------------------------------------

Do you already have a patch?
see https://thrift.apache.org/docs/HowToContribute

> 'configure' script does not honor --with-openssl=<path> for libcrypto for BN_init
> ---------------------------------------------------------------------------------
>
>                 Key: THRIFT-3555
>                 URL: https://issues.apache.org/jira/browse/THRIFT-3555
>             Project: Thrift
>          Issue Type: Bug
>          Components: Build Process
>    Affects Versions: 0.9.3
>            Reporter: Peter Butler
>
> When running the 'configure' script to set up the thrift build environment, the path supplied to the 'with-openssl=<path>' option is not honored for all tests within the script where libcrypto is required.
> For the first part of the script the path is indeed honored.  For example, at line 17316 ("checking whether compiling and linking against OpenSSL works") it can be easily validated (via strace and/or bash script debugging) that the correct user-supplied path to a particular OpenSSL library is being used.
> However, later in the script, at line 23292 ("checking for BN_init in -lcrypto...") this is not the case.  Again this can readily verified (via strace and/or bash script debugging) that the user supplied path is skipped entirely, and only the O/S system-defined default library paths are searched for libcrypto.



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