[Lldb-commits] [lldb] r213158 - Add kalimba as a platform.

[Matthew Gardiner]

Todd Fiala wrote:
> Hi Matthew,
>
> On Thu, Jul 17, 2014 at 10:30 PM, Matthew Gardiner <mg11 at csr.com 
> <mailto:mg11 at csr.com>> wrote:
>
>     Todd Fiala wrote:
>
>         Hey Matthew,
>
>         I'm thrilled that you are trying to get a test Linux box up!
>
>         The easiest way to run that depends on whether you're using
>         cmake/ninja or configure/make.  If you don't have a strong
>         preference, going with cmake/ninja is definitely the faster
>         way to go.
>
>         In any event, you'll want to kick off the tests with either
>         one of these, after you've done a full build (i.e. 'ninja' in
>         the build dir or 'make' in the build dir):
>
>         cmake/ninja:
>         cd /your/build/dir
>         ninja check-lldb
>
>     I think I'm going to stick with make for now, since I've never had
>     any luck with cmake/ninja.
>
>
> Ok.  I'm eventually going to document our setup, at which point you 
> can maybe try out cmake again.  Using ninja as the builder is 
> significantly faster (I think it was 20%+ faster for us over make).
>
>         configure/make:
>         cd /your/llvm/dir
>         cd tools/lldb/test
>         make
>
>
>     Ok... From what you've just said. Does that mean I'll running the
>     make in that tools/lldb/test runs the swig and python required to
>     get lldb.py built?
>
>
> Assuming I have the typical llvm, llvm/tools/clang and llvm/tools/lldb 
> directory structure for the source, I make a sibling directory to llvm 
> called build.  I cd into that, type something like:
> ../llvm/configure --prefix=`pwd`/../install
>
> Then I build with:
> make -j32
>
> (You'll want a j value that is something appropriate for your # cores 
> - I typically use n, where n is the number of cores I have, 32 in this 
> case).
>
> That will build everything, including the lldb python module, 
> liblldb.so (referenced by the lldb python module), and all the lldb exes.
>
> Then I run make in the  tools/lldb/test directory with this:
> make -C tools/lldb/test
>
> That should run all the tests for you.
>
> If I got any of the details wrong, I think it is covered here under 
> 'To build with autoconf' (including the autoconf-based testing):
>
> http://lldb.llvm.org/build.html
>
> Hope that helps!
>
>
>         Both those incantations will get you a test run that does the
>         tests without you needing to set up anything else (e.g.
>         lldb/python paths, or architecture settings for the test run).
>          They'll also run the tests faster if you have multiple cores
>         on your dev box/VM.
>
>         Let me know if you hit any trouble with that.
>
>
>     Yeah - will do. I'm going to try to focus this today.
>
>
> Good luck!
>
>
>         Particularly the cmake configuration line - the basic cmake
>         configuration line with minimal options has never worked well
>         for me on Linux, so I call it with a bunch of flags to specify
>         the llvm build type and a few other details.
>
>     No. I've never had much luck with cmake :-(
>
>
> Yeah, it took me several days to get my cmake setup working back on 
> Ubuntu 12.04.  It's a bit easier on Ubuntu 14.04.
>
>     Anyway, I'm kicking off a fresh lldb build (i.e. configure in the
>     out-of-tree build dir, then a make) now. And I'll postback later
>     on today regarding my progress.
>
>     Later
>
>     Matt
>
>
> Let me know how it goes!

I just got this:


Well, so my regular llvm/lldb build completed:

So I cd to the tools/lldb/test in my *build* directory, then run make

~/src/main/build/tools/lldb/test

[0][][main][] > make
rm -rf lldb-test-traces
python /home/mg11/src/main/llvm/tools/lldb/test/dosep.ty -o 
"--executable /home/mg11/src/main/build/Debug+Asserts/bin/lldb -q -s 
lldb-test-traces -u CXXFLAGS -u CFLAGS -C gcc"
This script requires lldb.py to be in either 
/home/mg11/src/main/llvm/tools/lldb/build/Debug/LLDB.framework/Resources/Python, 
/home/mg11/src/main/llvm/tools/lldb/build/Release/LLDB.framework/Resources/Python, 
or 
/home/mg11/src/main/llvm/tools/lldb/build/BuildAndIntegration/LLDB.framework/Resources/Python
...
This script requires lldb.py to be (this line being repeated lot)
...
...
...
Ran 299 tests.
Failing Tests (299)
FAIL: LLDB (suite) :: TestSTTYBeforeAndAfter.py (Linux 
mg11-fc20.root.pri 3.13.7-200.fc20.x86_64 #1 SMP Mon Mar 24 22:01:49 UTC 
2014 x86_64 x86_64)
FAIL: LLDB (suite) :: TestLogging.py (Linux mg11-fc20.root.pri 
3.13.7-200.fc20.x86_64 #1 SMP Mon Mar 24 22:01:49 UTC 2014 x86_64 x86_64)
FAIL: LLDB (suite) :: TestSourceManager.py (Linux mg11-fc20.root.pri 
3.13.7-200.fc20.x86_64 #1 SMP Mon Mar 24 22:01:49 UTC 2014 x86_64 x86_64)
...
presumably all the failed tests are now being listed?
FAIL: LLDB (suite) :: TestPluginCommands.py (Linux mg11-fc20.root.pri 
3.13.7-200.fc20.x86_64 #1 SMP Mon Mar 24 22:01:49 UTC 2014 x86_64 x86_64)
make: *** [check-local] Error 1

[0][][main][] >

So it looks as if all my tests failed. Does lldb i.e. 
~/src/main/build/Debug+Asserts/bin need to be in the path when running 
make in the test dir?

Matt



Member of the CSR plc group of companies. CSR plc registered in England and Wales, registered number 4187346, registered office Churchill House, Cambridge Business Park, Cowley Road, Cambridge, CB4 0WZ, United Kingdom
More information can be found at www.csr.com. Keep up to date with CSR on our technical blog, www.csr.com/blog, CSR people blog, www.csr.com/people, YouTube, www.youtube.com/user/CSRplc, Facebook, www.facebook.com/pages/CSR/191038434253534, or follow us on Twitter at www.twitter.com/CSR_plc.
New for 2014, you can now access the wide range of products powered by aptX at www.aptx.com.