summaryrefslogtreecommitdiffstats
path: root/llvm/lib/Object/FunctionIndexObjectFile.cpp
diff options
context:
space:
mode:
authorZachary Turner <zturner@google.com>2015-11-02 22:13:13 +0000
committerZachary Turner <zturner@google.com>2015-11-02 22:13:13 +0000
commita7cd16b252c68bd7e79ba52bdab8f5c377ca4fd2 (patch)
tree4a837270107df75b113a7db9654a24bf41911ae9 /llvm/lib/Object/FunctionIndexObjectFile.cpp
parentd7153101621bd09b6f07371a75c0f316085e8e62 (diff)
downloadbcm5719-llvm-a7cd16b252c68bd7e79ba52bdab8f5c377ca4fd2.tar.gz
bcm5719-llvm-a7cd16b252c68bd7e79ba52bdab8f5c377ca4fd2.zip
Revert part of r239007 related to creating the Python symlink.
This has apparently been broken since June, but only on non-Windows. Perhaps nobody noticed it because if the symlink is already there it won't try to re-create it, and nobody ever tried doing a clean build. In any case, I will let the original author attempt to fix this if he is still interested. the problem is that in the normal case of not setting BUILD_SHARED_LIBS and simply running ninja, it would link _lldb.so to a non-existent location, creating a dangling symlink. llvm-svn: 251840
Diffstat (limited to 'llvm/lib/Object/FunctionIndexObjectFile.cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud