Comment 3 for bug 1293295

I should mention the current configurations that the MacPorts build bots are using (all build successfully, those using -std=c++11 fail without the patch) :

OS X 10.6
Xcode 4.2 (Build 4C199)
llvm-gcc: i686-apple-darwin10-llvm-gcc-4.2 (GCC) 4.2.1 (Based on Apple Inc. build 5658) (LLVM build 2336.1.00) without any '-std=c++11'

OS X 10.7
Xcode 4.6.3 (build 4H1503)
Apple LLVM version 4.2 (clang-425.0.28) (based on LLVM 3.2svn) '-std=c++11 -stdlib=libstdc++'

OS X 10.8
Xcode 5.0.2 (build 5A3005)
Apple LLVM version 5.0 (clang-500.2.79) (based on LLVM 3.3svn) '-std=c++11 -stdlib=libstdc++'

OS X 10.9
Xcode 5.0.2 (build 5A3005)
Apple LLVM version 5.0 (clang-500.2.79) (based on LLVM 3.3svn) '-std=c++11 -stdlib=libc++'

In addition, I, personally, have successfully built (with the patch, fails without) on

OS X 10.8
Xcode 5.1 (build 5B130a )
Apple LLVM version 5.1 (clang-503.0.38) (based on LLVM 3.4svn) '-std=c++11 -stdlib=libstdc++'

OS X 10.9
Xcode 5.1 (build 5B130a )
Apple LLVM version 5.1 (clang-503.0.38) (based on LLVM 3.4svn) '-std=c++11 -stdlib=libc++'

I note also that this patch does not introduce any new C++11 only features, just makes the code compatible with
with the C++11 standard (as interpreted by clang).