[lldb-dev] ninja check-lldb failing due to lldb.py

David Blaikie dblaikie at gmail.com
Mon Mar 16 20:54:51 PDT 2015

On Mon, Mar 16, 2015 at 8:49 PM, Zachary Turner <zturner at google.com> wrote:

> I really need to fix this error message, it hit Rafael last time too.

Well it did seem to be part of a longer error message, but perhaps they
were unrelated:

This script requires lldb.py to be in either
or /mnt/fast/dev/llvm/src/tools/l
ldb/build/BuildAndIntegration/LLDB.framework/Resources/Python. Some tests
might fail.
Traceback (most recent call last):
  File "/mnt/fast/dev/llvm/src/tools/lldb/test/dotest.py", line 1322, in
    os.path.walk(testdir, visit, 'Test')
  File "/usr/lib/python2.7/posixpath.py", line 238, in walk
    func(arg, top, names)
  File "/mnt/fast/dev/llvm/src/tools/lldb/test/dotest.py", line 1219, in
  File "/mnt/fast/dev/llvm/src/tools/lldb/test/unittest2/loader.py", line
111, in loadTestsFromName
    module = __import__('.'.join(parts_copy))
line 7, in <module>
    import lldb
ImportError: No module named lldb

> Basically ignore it, the message is totally wrong. What does lldb -P say?

$ ~/dev/llvm/build/clang/debug/split/notypes/nostandalone/bin/lldb -P
Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "/usr/local/buildtools/current/sitecustomize/sitecustomize.py", line
181, in SetupPathsAndImport
    return real_import(name, globals, locals, fromlist, level)
ImportError: No module named lldb.embedded_interpreter

> On Mon, Mar 16, 2015 at 8:21 PM David Blaikie <dblaikie at gmail.com> wrote:
>> I have a standard source layout:
>> llvm
>>  \- src
>>    \- tools
>>      \- clang
>>      \- lldb
>>  \- build
>>    \- ...
>> llvm/build$ ninja check-lldb
>> This script requires lldb.py to be in either
>> llvm/src/tools/lldb/build/Debug/LLDB.framework/Resources/Python,
>> llvm/src/tools/lldb/build/Release/LLDB.framework/Resources/Python, or
>> llvm/src/tools/lldb/build/BuildAndIntegration/LLDB.framework/Resources/Python.
>> Some tests might fail."
>> What do these 3 directories have to do with anything when my build
>> directory is llvm/build, not llvm/src/tools/lldb/build ? & is this a manual
>> step I'm meant to undertake? (could we automate it?)
>> (& the check-lldb target doesn't have dependencies on all the tools
>> required to run the tests either - which isn't quite right (compared to
>> check-llvm, check-clang, etc))
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/lldb-dev/attachments/20150316/1fcedb03/attachment.html>

More information about the lldb-dev mailing list