mac os x lldb compiler version


I'd like to build LLDB on Mac OS X 10.8 with the same compiler that's used by the buildbot at:

However, from the latest builds I notice that clang's version is:

Apple clang version 4.1 (tags/Apple/clang-421.11.66) (based on LLVM 3.1svn)

meanwhile, on a local machine with all the xcode updates installed, my clang is slightly older than that:

Apple clang version 4.1 (tags/Apple/clang-421.11.65) (based on LLVM 3.1svn)

Is it possible that clang 421.11.66 is in fact released and we just didn't get the update (the mac in question is plugged into the Canadian App Store)? I'm seeing lots of warnings related to c++11 features such as:
OptionValueEnumeration.h:37:13: warning: 'typename' occurs outside of a template [-Wc++11-extensions]

and also one error on a lambda in OptionGroupVariable.cpp:45:13: error: expected expression...

I suspect the error and warnings are due to my older clang lacking some lambda support (I checked CLANG_CXX_LANGUAGE_STANDARD=c++0x) but I'm not sure how to verify this as the tag clang-421.11.65 is not public and I'm not sure how it correlates to an SVN revision.

Anyways, I'm happy to wait until the next xcode update to resolve the version mismatch, but if the official darwin buildbot is going to always use a pre-release compiler to build LLDB, it's going to be a challenge for us Linux folk to test our changes on Mac OS X. Any guidance?

Thanks a bunch,

Daniel Malea <<>>
Intel Waterloo
Phone: 519-772-2566

I did a fresh install of Xcode 4.5.2 on my home mac from the App store to verify, yes clang-421.11.66 is installed with the current public release version.

$ xcodebuild -version
Xcode 4.5.2
Build version 4G2008a

$ xcrun clang -v
Apple clang version 4.1 (tags/Apple/clang-421.11.66) (based on LLVM 3.1svn)
Target: x86_64-apple-darwin12.3.0
Thread model: posix

You may also need to download the command line tools to update the clang in /usr/bin

Oops, sorry about jumping to conclusions! I too am seeing the correct clang version on a different machine. My weird build problems are resolved after cleaning out the source/build dirs of LLDB :slight_smile:

Happy new year,