[lldb-dev] Linux build broken by clang commit - r170482
sean at crittercism.com
Thu Dec 20 21:50:20 PST 2012
Was in the process of building lldb on linux for the first time and finally
got stuck on compilation errors in Expression/ClangASTSource.cpp.
It looked to me like the code was expecting an STL pair but getting a
fundamentally different type. (I think) I eventually tracked it down to
this commit -
which looks like a non-trivial change to me (though I'm hardly well versed
in llvm/clang/lldb code).
Apparently there is a linux build bot run at uuic, which was experiencing
the same error I was - here is the first broken build:
A few questions - It seems to me that lldb used to purposely tie itself to
specific revisions of llvm and clang to avoid the instability of an
actively developed project, though some time in the past few months things
changed such that lldb trunk should always build against llvm and clang's
trunk revisions. Out of curiosity, is there no reciprocity between the llvm
and clang developers? It seems like that change would have not passed
build/regression tests against lldb.
Since it's the holiday season, I'm not going to hold my breath on a patch -
is my best bet just going back to the last revision of of lldb that built,
and syncing to the closest SVN revisions for clang and llvm at that time?
Would appreciate any suggestions from someone who builds and uses lldb on
(BTW, sorry for pointing this out and not submitting a patch, but I don't
think I'd be able to wrap my head around everything fast enough to fix this
one. Thanks for all of your contributions though!)
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the lldb-dev