[llvm-commits] Improved Covered Default Switch detection

[Óscar Fuentes]

Joe Abbey <joe.abbey at gmail.com> writes:

>> How did you end up in this situation?  Something has gone very wrong
>> if the build system finds clang++ but not clang.
>> 
>
> I don't think I've done anything terribly unique.  
>
> 1) Install Xcode
>
> 2) Installing command-line tools
>
> jabbeymbp:llvmCommit jabbey$ ls -l /usr/bin/gcc /usr/bin/g++ /usr/bin/c++ /usr/bin/cc
> lrwxr-xr-x  1 root  wheel   7 Nov 20 01:16 /usr/bin/c++ -> clang++
> lrwxr-xr-x  1 root  wheel   5 Nov 20 01:16 /usr/bin/cc -> clang
> lrwxr-xr-x  1 root  wheel  12 Nov 20 01:17 /usr/bin/g++ -> llvm-g++-4.2
> lrwxr-xr-x  1 root  wheel  12 Nov 20 01:17 /usr/bin/gcc -> llvm-gcc-4.2
> jabbeymbp:llvmCommit jabbey$ xcode-select --print-path
> /Applications/Xcode.app/Contents/Developer
> jabbeymbp:llvmCommit jabbey$ cmake --version
> cmake version 2.8.8
>
> Is this not as expected?

I don't think so. Unless you ask for something different, CMake should
use c++ (->clang++) for C++ and cc (->clang) for C as defaults. Doing
otherwise looks like a bug. Unless OSX has a tradition of broken or
inferior cc which makes gcc preferable.

BTW, what I mentioned on my other message was on Linux.