Dan Burkert has submitted this change and it was merged.

Change subject: Bump squeasel version
......................................................................


Bump squeasel version

The new version of squeasel goes back to using dlopen for OpenSSL, which fixes
an issue we have hit on Centos 6 with incompatible OpenSSL versions:

Between Centos 6.4 and 6.6 the OpenSSL version was bumped from 1.0.0 to 1.0.1e.
Between the 1.0.0 and 1.0.1e versions, Red Hat introduced symbol versioning for
OpenSSL, which results in any application which is compiled against the newer
version being incompatible with the older version at runtime (or installation
time as the rpm tool knows about the symbol version dependency). As part of 
moving
to C++11, Kudu recently changed from building releases on Centos 6.4 to Centos
6.6 (and consequently from compiling against OpenSSL 1.0.0 to OpenSSL 1.0.1e).
The result is that Kudu RPMs are failing to install on Centos 6.4. Switching to
dynamic opening of OpenSSL in Squeasel breaks the direct dependency chain, and
allows packaged Kudu to once again work on Centos 6.4.

Change-Id: I5a9903703c3c97e3cc70640a82662ed14dc233fa
Reviewed-on: http://gerrit.cloudera.org:8080/1849
Reviewed-by: Adar Dembo <[email protected]>
Tested-by: Internal Jenkins
---
M CMakeLists.txt
M cmake_modules/FindSqueasel.cmake
M src/kudu/server/CMakeLists.txt
M thirdparty/build-definitions.sh
M thirdparty/vars.sh
5 files changed, 7 insertions(+), 26 deletions(-)

Approvals:
  Internal Jenkins: Verified
  Adar Dembo: Looks good to me, approved



-- 
To view, visit http://gerrit.cloudera.org:8080/1849
To unsubscribe, visit http://gerrit.cloudera.org:8080/settings

Gerrit-MessageType: merged
Gerrit-Change-Id: I5a9903703c3c97e3cc70640a82662ed14dc233fa
Gerrit-PatchSet: 4
Gerrit-Project: kudu
Gerrit-Branch: master
Gerrit-Owner: Dan Burkert <[email protected]>
Gerrit-Reviewer: Adar Dembo <[email protected]>
Gerrit-Reviewer: Dan Burkert <[email protected]>
Gerrit-Reviewer: Internal Jenkins
Gerrit-Reviewer: Todd Lipcon <[email protected]>

Reply via email to