krytarowski updated this revision to Diff 86828.
krytarowski added a comment.
LLDB_USE_SYSTEM_SIX approach
Repository:
rL LLVM
https://reviews.llvm.org/D29405
Files:
cmake/modules/LLDBConfig.cmake
scripts/CMakeLists.txt
scripts/Python/finishSwigPythonLLDB.py
Index: scripts/Python/fin
krytarowski added a comment.
In https://reviews.llvm.org/D29405#663566, @labath wrote:
> It does not seem to work for me. I get this when I run ninja check-lldb in
> the build directory:
>
> Traceback (most recent call last):
> File "/usr/local/google/home/labath/ll/llvm/tools/lldb/test/do
labath added a comment.
It does not seem to work for me. I get this when I run ninja check-lldb in the
build directory:
Traceback (most recent call last):
File "/usr/local/google/home/labath/ll/llvm/tools/lldb/test/dotest.py",
line 6, in
import lldbsuite.test
File
"/usr/local/
krytarowski added a comment.
Please help to test this patch for regressions, at the moment I don't have all
the test suits passing and I might have miss something.
At least `scripts/Python/modify-python-lldb.py` had to retain 'import six'.
Repository:
rL LLVM
https://reviews.llvm.org/D29405
krytarowski created this revision.
krytarowski added a project: LLDB.
The current version of LLDB installs six.py into global python library
directory. This approach produces conflicts downstream with distribution's
py-six copy.
Install six.py into subdirectory as this is a common way of handli
