summaryrefslogtreecommitdiffstats
path: root/llvm/lib/Target/ARM/Disassembler/ARMDisassembler.cpp
diff options
context:
space:
mode:
authorMichal Gorny <mgorny@gentoo.org>2017-08-03 19:41:33 +0000
committerMichal Gorny <mgorny@gentoo.org>2017-08-03 19:41:33 +0000
commitc1a0c00d50173a0f42b8fe0f36c642cefc14ada6 (patch)
treeb10ee3b4ded379d08dc57643a94f0bd87d585c5c /llvm/lib/Target/ARM/Disassembler/ARMDisassembler.cpp
parentd72c5e54c06a6ff398ea2d45d4d8f16ae434887a (diff)
downloadbcm5719-llvm-c1a0c00d50173a0f42b8fe0f36c642cefc14ada6.tar.gz
bcm5719-llvm-c1a0c00d50173a0f42b8fe0f36c642cefc14ada6.zip
[test] Fix clang library dir in LD_LIBRARY_PATH For stand-alone build
Prepend the clang library directory (determined using SHLIBDIR, alike in clang) to the LD_LIBRARY_PATH to ensure that just-built clang libraries will be used instead of a previous installed version. When a stand-alone build is performed, LLVM_LIBS_DIR contains the path to installed LLVM library directory. The same directory frequently contains a previously installed version of clang. SHLIBDIR, on the other hand, is always the build-tree directory, and therefore contains the freshly built clang libraries. In a non-stand-alone build, both paths will be the same and therefore including them both will not cause any issues. Differential Revision: https://reviews.llvm.org/D30155 llvm-svn: 309979
Diffstat (limited to 'llvm/lib/Target/ARM/Disassembler/ARMDisassembler.cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud