Igor GaliÄ wrote: > n.b.: Right now, this does not work, because our code has long since > (v2.1.4/TS-427) parted with clang compatibility. > XXX: Why are we not checking for clang on darwin? Isn't XCode the > default.. thing? Doesn't it come with clang? How often more will I > write clang in this commit message? Questions...
Trunk compiles on my Mac using XCode without problem... Maybe Apple made changes to make it "compatible" with gcc? I use Using built-in specs. Target: i686-apple-darwin11 Configured with: /private/var/tmp/llvmgcc42/llvmgcc42-2336.1~22/src/configure --disable-checking --enable-werror --prefix=/Developer/usr/llvm-gcc-4.2 --mandir=/share/man --enable-languages=c,objc,c++,obj-c++ --program-prefix=llvm- --program-transform-name=/^[cg][^.-]*$/s/$/-4.2/ --with-slibdir=/usr/lib --build=i686-apple-darwin11 --enable-llvm=/private/var/tmp/llvmgcc42/llvmgcc42-2336.1~22/dst-llvmCore/Developer/usr/local --program-prefix=i686-apple-darwin11- --host=x86_64-apple-darwin11 --target=i686-apple-darwin11 --with-gxx-include-dir=/usr/include/c++/4.2.1 Thread model: posix gcc version 4.2.1 (Based on Apple Inc. build 5658) (LLVM build 2336.1.00) I guess I'm to blame for breaking clang building ... I'm curious though, what is it that we're "missing" from not supporting clang? I mean, yes, we should support it, but is there really something we'd change in our code to take advantage of something clang specific? -- Leif
