diff options
| author | Fangrui Song <i@maskray.me> | 2022-03-25 14:56:18 -0700 |
|---|---|---|
| committer | Fangrui Song <i@maskray.me> | 2022-03-25 14:56:18 -0700 |
| commit | afaefb671fe12e7788d3e8de6b6193b935fbf16c (patch) | |
| tree | 7aefcfc0a5e152dfee99e420b158c63b63cb4588 /lldb/test/Shell/ScriptInterpreter/Python | |
| parent | 6c2be885ff1c62991a87858c1948ee0a86c57fa0 (diff) | |
| download | llvm-afaefb671fe12e7788d3e8de6b6193b935fbf16c.zip llvm-afaefb671fe12e7788d3e8de6b6193b935fbf16c.tar.gz llvm-afaefb671fe12e7788d3e8de6b6193b935fbf16c.tar.bz2 | |
[Driver][Linux] Remove D.Dir+"/../lib" from default search paths for LLVM_ENABLE_RUNTIMES builds
The rule was added in 2014 to support -stdlib=libc++ and -lc++ without
specifying -L, when D.Dir is not a well-known system library directory like
/usr/lib /usr/lib64. This rule turns out to get in the way with (-m32 for
64-bit clang) or (-m64 for 32-bit clang) for Gentoo :
https://github.com/llvm/llvm-project/issues/54515
Nowadays LLVM_ENABLE_RUNTIMES is the only recommended way building libc++ and
LLVM_ENABLE_PROJECTS=libc++ is deprecated. LLVM_ENABLE_RUNTIMES builds libc++
in D.Dir+"/../lib/${triple}/". The rule is unneeded. Also reverts D108286.
Gentoo uses a modified LLVM_ENABLE_RUNTIMES that installs libc++.so in
well-known paths like /usr/lib64 and /usr/lib which are already covered by
nearby search paths.
Implication: if a downstream package needs something like -lLLVM-15git and uses
libLLVM-15git.so not in a well-known path, it needs to supply -L
D.Dir+"/../lib" explicitly (e.g. via LLVMConfig.cmake), instead of relying on
the previous default search path.
Reviewed By: mgorny
Differential Revision: https://reviews.llvm.org/D122444
Diffstat (limited to 'lldb/test/Shell/ScriptInterpreter/Python')
0 files changed, 0 insertions, 0 deletions
