summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/functionalities
diff options
context:
space:
mode:
authorMichal Gorny <mgorny@gentoo.org>2016-11-01 20:31:52 +0000
committerMichal Gorny <mgorny@gentoo.org>2016-11-01 20:31:52 +0000
commitf77a9889c08124dbf27d883100008f3b1c09962b (patch)
tree5903fbce540950416c9c60ec128ad8e73dfcd719 /lldb/packages/Python/lldbsuite/test/functionalities
parent6dc7fcbec428fbc15be90bb9ff942f93752e04c1 (diff)
downloadbcm5719-llvm-f77a9889c08124dbf27d883100008f3b1c09962b.tar.gz
bcm5719-llvm-f77a9889c08124dbf27d883100008f3b1c09962b.zip
[test] Fix detecting LLVM zlib support in stand-alone builds
Fix the test run to declare missing HAVE_LIBZ value in stand-alone builds, using the LLVM_ENABLE_ZLIB that is exported in LLVMConfig.cmake. When using in-tree builds, HAVE_LIBZ is declared in cmake/config-ix.cmake as a result of LLVM's CMake checks. When building stand-alone, this value is not available and as a result caused clang to wrongly assume that LLVM was built without zlib support. To fix it, set it to the value of LLVM_ENABLE_ZLIB. While this variable is originally used to control the user preference, LLVM updates its value to 0 if zlib checks fail. Therefore, we can use it to reliably determine whether LLVM was built with zlib support or not. Differential Revision: https://reviews.llvm.org/D24869 llvm-svn: 285741
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/functionalities')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud