[Lldb-commits] [PATCH] D64881: [Cmake] Use the modern way to find Python when possible

Jonas Devlieghere via Phabricator via lldb-commits lldb-commits at lists.llvm.org
Wed Jul 17 14:35:11 PDT 2019

JDevlieghere added a comment.

In D64881#1590273 <https://reviews.llvm.org/D64881#1590273>, @stella.stamenova wrote:

> Re: Windows CMake: I am not sure, I'd have to do look into it further.
> On a separate note: I haven't looked into it yet, but we have a setup to run the LLDB tests on Ubuntu and that started failing somewhat recently with some Swig and Python errors. For example:
>   Unable to load lldb extension module.  Possible reasons for this include:
>     1) LLDB was built with LLDB_DISABLE_PYTHON=1
>     2) PYTHONPATH and PYTHONHOME are not set correctly.  PYTHONHOME should refer to
>        the version of Python that LLDB built and linked against, and PYTHONPATH
>        should contain the Lib directory for the same python distro, as well as the
>        location of LLDB's site-packages folder.
>     3) A different version of Python than that which was built against is exported in
>        the system's PATH environment variable, causing conflicts.
>     4) The executable '/home/e2admin/vstsdrive/_work/29/b/bin/lldb' could not be found.  Please check 
>        that it exists and is executable.
>   Traceback (most recent call last):
>     File "/home/e2admin/vstsdrive/_work/29/s/lldb/test/dotest.py", line 7, in <module>
>       lldbsuite.test.run_suite()
>     File "/home/e2admin/vstsdrive/_work/29/s/lldb/packages/Python/lldbsuite/test/dotest.py", line 1268, in run_suite
>       import lldb
>   ImportError: No module named 'lldb'
> I am  not sure how this change is going to affect that - better or worse?

Yes, this should solve (3). However, this should;ve already been caught at configure-time by my change in https://reviews.llvm.org/rL366243.




More information about the lldb-commits mailing list