[
https://issues.apache.org/jira/browse/THRIFT-3555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15105527#comment-15105527
]
Aki Sukegawa edited comment on THRIFT-3555 at 1/18/16 5:09 PM:
---------------------------------------------------------------
No it's not added recently.
I guess it's being excluded from release archives because it's only for
developers.
I recommend downloading the file from github if you want to avoid git clone.
Alternatively running {{autoreconf -if}} may be enough.
was (Author: nsuke):
No it's not added recently.
I guess it's being excluded from release archives because it's only for
developers.
I recommend downloading the file from github if you want to avoid git clone.
> '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
> Assignee: Aki Sukegawa
>
> 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)
