hadoop-mapreduce-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Purtell (JIRA)" <j...@apache.org>
Subject [jira] [Created] (MAPREDUCE-4769) Pipes build problem with recent OpenSSL libs
Date Sat, 03 Nov 2012 02:40:12 GMT
Andrew Purtell created MAPREDUCE-4769:

             Summary: Pipes build problem with recent OpenSSL libs
                 Key: MAPREDUCE-4769
                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4769
             Project: Hadoop Map/Reduce
          Issue Type: Bug
          Components: pipes
    Affects Versions: 3.0.0, 2.0.3-alpha
         Environment: CentOS 6.2 x86_64
            Reporter: Andrew Purtell

Seems to be a problem with CMake not figuring that the linker needs -lcrypto too with recent
OpenSSL. Observed on two CentOS 6 build servers occurring after 'yum update' pulled down an
openssl-devel update.

         [exec] Linking CXX executable examples/pipes-sort
         [exec] /usr/bin/cmake -E cmake_link_script CMakeFiles/pipes-sort.dir/li
         [exec] /usr/bin/c++    -g -Wall -O2 -D_REENTRANT -D_FILE_OFFSET_BITS=64
         [exec] /usr/bin/ld: libhadooppipes.a(HadoopPipes.cc.o): undefined refer
         [exec] /usr/bin/ld: note: 'BIO_ctrl' is defined in DSO /lib64/libcrypto
         [exec] /lib64/libcrypto.so.10: could not read symbols: Invalid operatio
         [exec] collect2: ld returned 1 exit status
         [exec] make[3]: *** [examples/pipes-sort] Error 1
         [exec] make[2]: *** [CMakeFiles/pipes-sort.dir/all] Error 2
         [exec] make[1]: *** [all] Error 2

This works around the problem:

diff --git hadoop-tools/hadoop-pipes/src/CMakeLists.txt hadoop-tools/hadoop-
index a1ee97d..29cfba7 100644
--- hadoop-tools/hadoop-pipes/src/CMakeLists.txt
+++ hadoop-tools/hadoop-pipes/src/CMakeLists.txt
@@ -71,5 +71,6 @@ add_library(hadooppipes STATIC
+    crypto


Builds with -Pnative won't complete without this.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message