[
https://issues.apache.org/jira/browse/ORC-371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16497174#comment-16497174
]
ASF GitHub Bot commented on ORC-371:
------------------------------------
Github user jamesclampffer commented on the issue:
https://github.com/apache/orc/pull/275
Rather than skipping the entire libhdfs++ build you could set the NO_SASL
parameter if openssl or cyrus is missing to build libhdfs++ without support for
strong authentication.
At one point someone added a partial implementation of SASL DIGEGT-MD5
directly in libhdfs++ and I think that may try to use SSL's RNG to generate
nonces (and looks like NO_SASL might not prevent that). If that breaks the
build with NO_SASL set we can get rid of that code in libhdfs++. Even if that
implementation worked it'd prevent the library from being FIPS 140-2 compliant
which is a deal breaker for my work.
> [C++] Disable Libhdfspp build when Cyrus SASL is not found
> ----------------------------------------------------------
>
> Key: ORC-371
> URL: https://issues.apache.org/jira/browse/ORC-371
> Project: ORC
> Issue Type: Bug
> Reporter: Deepak Majeti
> Assignee: Deepak Majeti
> Priority: Major
>
> Currently, the build fails with the following error
> -- Could NOT find CYRUS_SASL (missing: CYRUS_SASL_SHARED_LIB
> CYRUS_SASL_INCLUDE_DIR)
> CMake Error: The following variables are used in this project, but they are
> set to NOTFOUND.
> Please set them or make sure they are set and tested correctly in the CMake
> files:
> CYRUS_SASL_SHARED_LIB (ADVANCED)
> linked by target "orc" in directory tools/orc/c++/src
> -- Configuring incomplete, errors occurred!
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
