aboutsummaryrefslogtreecommitdiff
path: root/lldb/packages/Python/lldbsuite/test/lldbpexpect.py
diff options
context:
space:
mode:
authorFangrui Song <i@maskray.me>2021-01-24 20:21:57 +0000
committerFangrui Song <i@maskray.me>2021-01-24 20:21:57 +0000
commit50830e50031b5420f09f79e82cf6ec984fb8328d (patch)
tree63724ae8667ea5fdbd64a068cbeb46a8ced57299 /lldb/packages/Python/lldbsuite/test/lldbpexpect.py
parent16baad8f4e02aea19224da0d397b2f72980b15da (diff)
downloadllvm-50830e50031b5420f09f79e82cf6ec984fb8328d.zip
llvm-50830e50031b5420f09f79e82cf6ec984fb8328d.tar.gz
llvm-50830e50031b5420f09f79e82cf6ec984fb8328d.tar.bz2
[lldb] Add -Wl,-rpath to make tests run with fresh built libc++
On my Debian machine, system libc++/libc++abi is not installed (`libc++1-9 libc++abi-9`), 21 check-lldb-api tests fail because -stdlib=libc++ linked executables cannot find runtime libc++.so.1 at runtime. Use the `-Wl,-rpath,$(LLVM_LIBS_DIR)` mechanism in `packages/Python/lldbsuite/test/make/Makefile.rules` (D58630 for NetBSD) to allow such tests compile/link with fresh libc++ built beside lldb. (A system libc++.so.1 is not guaranteed to match fresh libc++ header files.) Some tweaks to the existing NetBSD rule when generalizing: * Drop `-L$(LLVM_LIBS_DIR)` since Clang driver adds it correctly. * Add `-stdlib=libc++` only for `USE_LIBCPP`. Also, drop `-isystem /usr/include/c++/v1` introduced in D9426. It is not needed by Clang driver. GCC using libc++ requires more setup. I don't find any test needing `-Wl,-rpath` in `test/Shell/helper/{build,toolchain}.py` (D58630 for NetBSD added them). Reviewed By: labath Differential Revision: https://reviews.llvm.org/D94888
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/lldbpexpect.py')
0 files changed, 0 insertions, 0 deletions