Re: "Future" of llvm-gcc with regards to support
Re: "Future" of llvm-gcc with regards to support
- Subject: Re: "Future" of llvm-gcc with regards to support
- From: Brad Oliver <email@hidden>
- Date: Mon, 27 Feb 2012 23:31:10 -0700
I'd file a bug report, but I'm not exactly sure what I'd file it on. "Make Clang versioning consistent" ?
Anyway, I just double-checked and Xcode 4.3 says the command-line tools were not installed. I could swear I did that immediately after installing Xcode 4.3 last week, but perhaps that only happened in a dream.
So after installing that, I get the expected "Apple clang version 3.1 (tags/Apple/clang-318.0.45) (based on LLVM 3.1svn)". My world makes a little more sense now, although I forgot to mention another versioning inconsistency:
GCC_VERSION is com.apple.compilers.llvm.clang.1_0 (again with the 1.0!)
On Feb 27, 2012, at 11:10 PM, Joar Wingfors wrote:
> Please file a bug report.
>
> (Are you sure that you're invoking the correct copy of clang when you're getting the version on the command line?)
>
> Joar
>
>
> On 27 feb 2012, at 12:05, Brad Oliver wrote:
>
>> On Feb 24, 2012, at 4:29 PM, Jean-Daniel Dupas wrote:
>>
>>> llvm-gcc is obsolete and has been deprecated in the LLVM 3.0 release (using the official LLVM versioning, not the fancy Apple one).
>>
>> OK, fair enough. Can someone explain to me the Clang versioning?
>>
>> * Taking Xcode 4.3 as an example, I see that it reports "Apple LLVM Compiler 3.1" as the default compiler.
>>
>> * I see warning messages in the build from "LLVM 1.0"
>>
>> * Running clang -v on the commandline gives me "Clang version 3.0 (based on LLVM 3.0svn).
>>
>> *head explodes*
--
Brad Oliver
email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden