You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Yi Liu (JIRA)" <ji...@apache.org> on 2014/10/21 11:02:34 UTC
[jira] [Created] (HADOOP-11216) Improve Openssl library finding
Yi Liu created HADOOP-11216:
-------------------------------
Summary: Improve Openssl library finding
Key: HADOOP-11216
URL: https://issues.apache.org/jira/browse/HADOOP-11216
Project: Hadoop Common
Issue Type: Improvement
Components: security
Affects Versions: 2.6.0
Reporter: Yi Liu
Assignee: Yi Liu
When we compile Openssl 1.0.0\(x\) or 1.0.1\(x\) using default options, there will be {{libcrypto.so.1.0.0}} in output lib dir, so we expect this version suffix in cmake build file
{code}
SET(STORED_CMAKE_FIND_LIBRARY_SUFFIXES CMAKE_FIND_LIBRARY_SUFFIXES)
set_find_shared_library_version("1.0.0")
SET(OPENSSL_NAME "crypto")
....
{code}
If we don't bundle the crypto shared library in Hadoop distribution, then Hadoop will try to find crypto library in system path when running.
But in real linux distribution, there may be no {{libcrypto.so.1.0.0}} or {{libcrypto.so}} even the system embedded openssl is 1.0.1\(x\). Then we need to make symbolic link.
This JIRA is to improve the Openssl library finding.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)