I can probably help better in person. But this means it can't load the lldb python extension module. Usually it's in build/lib/site-packages/lldb and it should be a symlink to build/bin/liblldb.so. If that looks ok, I vaguely recall something about the lib suffix for 64 bit builds, but it's not coming to me right now. Chandler probably remembers.<br><div class="gmail_quote">On Mon, Mar 16, 2015 at 8:54 PM David Blaikie <<a href="mailto:dblaikie@gmail.com">dblaikie@gmail.com</a>> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Mon, Mar 16, 2015 at 8:49 PM, Zachary Turner <span dir="ltr"><<a href="mailto:zturner@google.com" target="_blank">zturner@google.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">I really need to fix this error message, it hit Rafael last time too. </blockquote></div></div></div><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div><br>Well it did seem to be part of a longer error message, but perhaps they were unrelated:<br><br>
<p><span>This script requires lldb.py to be in either /mnt/fast/dev/llvm/src/tools/lldb/build/Debug/LLDB.framework/Resources/Python, /mnt/fast/dev/llvm/src/tools/lldb/build/Release/LLDB.framework/Resources/Python, or /mnt/fast/dev/llvm/src/tools/l<br></span>ldb/build/BuildAndIntegration/LLDB.framework/Resources/Python. Some tests might fail.<br>Traceback (most recent call last):<br> File "/mnt/fast/dev/llvm/src/tools/lldb/test/dotest.py", line 1322, in <module><br> os.path.walk(testdir, visit, 'Test')<br> File "/usr/lib/python2.7/posixpath.py", line 238, in walk<br> func(arg, top, names)<br> File "/mnt/fast/dev/llvm/src/tools/lldb/test/dotest.py", line 1219, in visit <br> suite.addTests(unittest2.defaultTestLoader.loadTestsFromName(base))<br> File "/mnt/fast/dev/llvm/src/tools/lldb/test/unittest2/loader.py", line 111, in loadTestsFromName<br> module = __import__('.'.join(parts_copy))<br> File "/mnt/fast/dev/llvm/src/tools/lldb/test/lang/objc/objc++/TestObjCXX.py", line 7, in <module><br> import lldb<br>ImportError: No module named lldb</p> </div></div></div></div><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"> Basically ignore it, the message is totally wrong. What does lldb -P say?</blockquote></div></div></div><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div><br>
<p><span>$ ~/dev/llvm/build/clang/debug/split/notypes/nostandalone/bin/lldb -P<br></span>Traceback (most recent call last):<br> File "<string>", line 1, in <module><br> File "/usr/local/buildtools/current/sitecustomize/sitecustomize.py", line 181, in SetupPathsAndImport<br> return real_import(name, globals, locals, fromlist, level)<br>ImportError: No module named lldb.embedded_interpreter<br>/mnt/fast/dev/llvm/build/clang/debug/split/notypes/nostandalone/bin/../lib/python2.7/site-packages</p> </div></div></div></div><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div><div><br><div class="gmail_quote">On Mon, Mar 16, 2015 at 8:21 PM David Blaikie <<a href="mailto:dblaikie@gmail.com" target="_blank">dblaikie@gmail.com</a>> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr">I have a standard source layout:<br><br>llvm<br> \- src<br> \- tools<br> \- clang<br> \- lldb<br> \- build<br> \- ...<br> <br>
<p><span>llvm/build$ ninja check-lldb<br>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."<br><br>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?)<br><br>(& 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))</span></p></div>
</blockquote></div>
</div></div></blockquote></div></div></div></blockquote></div>