[ https://issues.apache.org/jira/browse/HADOOP-12845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15174021#comment-15174021 ]
Colin Patrick McCabe commented on HADOOP-12845: ----------------------------------------------- There was a long discussion about this on HADOOP-11216. Basically, we don't want to have to build custom packages for each minor release of each Linux distribution. But, on the other hand, there is no standardized naming scheme for openssl... some distros have libcrypto.so.10, some have libcrypto.so.1.0.0, some have libcrypto.so.1.0.0e. That's why we settled on just linking against the no-extension version (i.e. the devel version). We could potentially have it check for whatever full library name it found during building, in addition to checking for the no-extension version. > Improve Openssl library finding on RedHat system > ------------------------------------------------ > > Key: HADOOP-12845 > URL: https://issues.apache.org/jira/browse/HADOOP-12845 > Project: Hadoop Common > Issue Type: Bug > Affects Versions: 2.7.2 > Reporter: Sebastien Barrier > Priority: Minor > > The issue is related to [https://issues.apache.org/jira/browse/HADOOP-11216]. > In the BUILDING.txt it's specified "Use -Drequire.openssl to fail the build > if libcrypto.so is not found". > On RedHat system (Fedora/Centos/...) the /usr/lib64/libcrypto.so is a link > provided by openssl-devel RPM package which is fine on a build/development > host, but devel packages are not supposed to be installed on Production > servers (Hadoop Cluster) and the openssl RPM package don't include that link > which is a problem. > # hadoop checknative -a > ... > openssl: false Cannot load libcrypto.so (libcrypto.so: cannot open shared > object file: No such file or directory)! > There's only /usr/lib64/libcrypto.so.10 but no /usr/lib64/libcrypto.so > Also trying to compile with "-Drequire.openssl > -Dopenssl.lib=/usr/lib64/libcrypto.so.10" failed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)