summaryrefslogtreecommitdiffstats
path: root/llvm/docs/CommandGuide/llvm-strings.md
diff options
context:
space:
mode:
authorLouis Dionne <ldionne@apple.com>2019-08-07 21:36:03 +0000
committerLouis Dionne <ldionne@apple.com>2019-08-07 21:36:03 +0000
commite0eed65e068ea053ab6a394c07c2a6da96ab7796 (patch)
tree1e53a5114ce879a42227df3bf897b261745ab765 /llvm/docs/CommandGuide/llvm-strings.md
parent1b1f1d66778b6428e31fb25a90c5beeaaee77c96 (diff)
downloadbcm5719-llvm-e0eed65e068ea053ab6a394c07c2a6da96ab7796.tar.gz
bcm5719-llvm-e0eed65e068ea053ab6a394c07c2a6da96ab7796.zip
[libc++] Take 3: Do not cleverly link against libc++abi just because it happens to be there
Summary: Otherwise, when libcxxabi is not an enabled project in the monorepo, we get a link error because we try to link against non-existent cxxabi_shared. More generally, we shouldn't change the behavior of the build based on implicit things like whether a file happens to be at a specific path or not. This is a re-application of r365222 that had been reverted in r365233 and then r365359 because it broke the build bots. The build bots should now specify explicitly what ABI library they want to use (libc++abi), so this commit should now be OK to merge. It takes a while for build bots to pick up configuration changes, which is why this failed the last time around. Differential Revision: https://reviews.llvm.org/D63883 llvm-svn: 368213
Diffstat (limited to 'llvm/docs/CommandGuide/llvm-strings.md')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud