summaryrefslogtreecommitdiffstats
path: root/polly/lib/CodeGen/PPCGCodeGeneration.cpp
diff options
context:
space:
mode:
authorMichal Gorny <mgorny@gentoo.org>2017-08-17 20:33:21 +0000
committerMichal Gorny <mgorny@gentoo.org>2017-08-17 20:33:21 +0000
commit8e58ad5182cb75ab14dc4f1b1ecc59892fd753ad (patch)
treeb366d1a65e4c44cea7b4ed2ab0eaa787c25211c9 /polly/lib/CodeGen/PPCGCodeGeneration.cpp
parenta2c4112791ba99f3fc38dfbce6d47dc1ccac2a5a (diff)
downloadbcm5719-llvm-8e58ad5182cb75ab14dc4f1b1ecc59892fd753ad.tar.gz
bcm5719-llvm-8e58ad5182cb75ab14dc4f1b1ecc59892fd753ad.zip
[cmake] Add explicit linkage from Core to curses
The Core library calls functions provided by the curses library. Add an appropriate explicit LINK_LIBS to ${CURSES_LIBRARIES} to propagate the dependency correctly within the build system. It seems that so far the linkage was handled by some kind of implicit magic LLDB_SYSTEM_LIBS variable. However, it stopped working for unittests as the curses libraries are passed before the LLDBCore library, resulting in `-Wl,--as-needed` stripping the yet-unused library before it is required by LLDBCore, and effectively breaking the build. I think it's better to focus on listing all the dependencies explicitly and let CMake propagate them rather than trying to figure out why this hack stopped working. This is also more consistent with LLVM where the curses linkage in LLVMSupport is expressed directly in the library rather than deferred to the final programs. Differential Revision: https://reviews.llvm.org/D36358 llvm-svn: 311122
Diffstat (limited to 'polly/lib/CodeGen/PPCGCodeGeneration.cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud