You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@impala.apache.org by "Sailesh Mukil (JIRA)" <ji...@apache.org> on 2017/11/27 18:00:08 UTC
[jira] [Resolved] (IMPALA-6220) Build broken due to ‘EVP_aes_256_ctr’ not declared in openssl-uitl.cc
[ https://issues.apache.org/jira/browse/IMPALA-6220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sailesh Mukil resolved IMPALA-6220.
-----------------------------------
Resolution: Fixed
Assignee: Michael Ho (was: Sailesh Mukil)
Fix Version/s: Impala 2.11.0
The broken build is fixed by reverting the offending commit. Let's continue the conversation for the fix in IMPALA-6128.
https://github.com/apache/incubator-impala/commit/3632ed4b9e90d7a7a10300fed4d5710ae72c6ebf
> Build broken due to ‘EVP_aes_256_ctr’ not declared in openssl-uitl.cc
> ---------------------------------------------------------------------
>
> Key: IMPALA-6220
> URL: https://issues.apache.org/jira/browse/IMPALA-6220
> Project: IMPALA
> Issue Type: Bug
> Components: Backend
> Reporter: Michael Ho
> Assignee: Michael Ho
> Labels: broken-build
> Fix For: Impala 2.11.0
>
>
> A lot of builds were broken due to the following compilation error. Most likely due to the following [commit|https://gerrit.cloudera.org/#/c/8510/]. [~sailesh], since you reviewed this change, can you please take a quick look ? cc'ing [~kexianda]
> {noformat}
> 00:30:11 /data/jenkins/workspace/impala-umbrella-build-and-test/repos/Impala/be/src/util/openssl-util.cc: In member function ‘impala::Status impala::EncryptionKey::EncryptInternal(bool, const uint8_t*, int64_t, uint8_t*) const’:
> 00:30:11 /data/jenkins/workspace/impala-umbrella-build-and-test/repos/Impala/be/src/util/openssl-util.cc:107:68: error: ‘EVP_aes_256_ctr’ was not declared in this scope
> 00:30:11 const EVP_CIPHER* evpCipher = IsCtrSupported() ? EVP_aes_256_ctr() : EVP_aes_256_cfb();
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)