Red Hat Bugzilla – Bug 803545
Last modified: 2012-10-27 13:21:52 EDT
Recently lldb team as work to enable lldb build under linux, as llvm provides clang will be great to do same for lldb.
Thabnks a lot
Note llvm 3.1 come soon
LLDB documentation does not mention Linux support yet, so I'm a bit hesitant about making it the default.
I need to reorganize the LLVM spec anyway -- need to find time to do that, so thanks for reminding me about this. I can make LLDB inclusion a build-time option, and you can test if it works for you -- how does that sound?
sound good :-)
thanks a lot for your works.
I have already in the past ask from LLVM mailling list to write a doc for linux but it is a bit slow in any case.
I see this bug with state Assigned . I would like to know what is the state ?
thanks a lot for your great job
Upstream still does not support Linux, and attempting to build from the latest trunk fails with type cast problems.
Please refrain from reopening this until there is proper Linux support for LLDB (or other LLVM technologies)
Thanks a lot for your try, i seen this how to http://lldb.llvm.org/build.html
The instructions there are, sadly, wrong.
- configure --enable-libcpp does not make much sense since libcxx's (they don't call it consistently) website claims they only support OS X
- the CXXFLAGS=-std=c++11 causes build to immediately fail with GCC
Looks like one can only build this with clang. Let me check with the packaging committee if we can have LLVM/clang self-hosting itself
ok thanks i search in same time some information.
So, it seem the current lldb trunk break the build on linux but rev 166514 should works
Without a patch to the spec and a mock build demonstrating that lldb actually builds, I don't have time to invest in this, sorry. Certainly not while upstream cannot even update the README, and the documentation barely mentions compiling with GCC.
Due to the critical use of LLVM to compile Mesa's LLVMpipe, we will not be switching to self-hosting LLVM and Clang anytime soon - unless someone wants to make it happen and is willing to take ownership of the switch. Until that happens, packaging LLDB will be a rather iffy proposition.