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.
---
