Re: [cmake-developers] Suspicious Clang versions

2013-10-08 Thread Brad King
On 08/06/2013 09:19 AM, Brad King wrote: On second thought adding yet another dimension to the compiler identification is just more complexity. We can use a separate compiler id for each variant and simply have the platform information modules for each vendor include the upstream one. I've

Re: [cmake-developers] Suspicious Clang versions

2013-08-15 Thread Rolf Eike Beer
Am 14.08.2013 08:12, schrieb Rolf Eike Beer: s...@rogue-research.com wrote: http://open.cdash.org/testDetails.php?test=201937829build=2986379 (MacOS 10.8) shows 3.4.0. But since even 3.4 does not seem to be released I wonder what's going on there? That one is the open source clang, which

Re: [cmake-developers] Suspicious Clang versions

2013-08-15 Thread Sean McBride
On Thu, 15 Aug 2013 10:15:11 +0200, Rolf Eike Beer said: http://open.cdash.org/testDetails.php?test=203678570build=2998892 Looks like the headers are not those that belong to that version of Clang, but older ones. To which headers do you refer? On that version of the OS and Xcode, I believe

Re: [cmake-developers] Suspicious Clang versions

2013-08-14 Thread Rolf Eike Beer
s...@rogue-research.com wrote: http://open.cdash.org/testDetails.php?test=201937829build=2986379 (MacOS 10.8) shows 3.4.0. But since even 3.4 does not seem to be released I wonder what's going on there? That one is the open source clang, which I build from svn. It's not from

Re: [cmake-developers] Suspicious Clang versions

2013-08-06 Thread Brad King
On 08/05/2013 03:45 PM, Brad King wrote: One of the main purposes of the compiler id is to load platform modules like Platform/os-id-lang and Compiler/id-lang. Most of the information in these files will be identical across the upstream and vendor-specific Clang distributions so having a

Re: [cmake-developers] Suspicious Clang versions

2013-08-05 Thread Rolf Eike Beer
s...@rogue-research.com wrote: Yeah, it's confusing... :( http://open.cdash.org/testDetails.php?test=201937899build=2986383 (MacOS 10.7) The CXX compiler identification is Clang 4.0.0 I do not believe that. Apple has their own fork/branch of clang which they use in Xcode.

Re: [cmake-developers] Suspicious Clang versions

2013-08-05 Thread Brad King
On 08/05/2013 02:08 AM, Rolf Eike Beer wrote: s...@rogue-research.com wrote: very confusingly, Apple uses their own version numbering scheme. So that's Apple clang 4.0. It comes with whatever version of Xcode that machine's running (4.4 I think?). any version checking like I do in the

Re: [cmake-developers] Suspicious Clang versions

2013-08-05 Thread Brad King
On 08/05/2013 09:26 AM, Stephen Kelly wrote: Brad King wrote: We need to fix this somehow or CMAKE_*_COMPILER_VERSION will be useless for Clang. Sean, is there any way to extract the underlying Clang version, perhaps with different preprocessor macros? We at least need to be able to detect

Re: [cmake-developers] Suspicious Clang versions

2013-08-05 Thread Sean McBride
On Mon, 5 Aug 2013 08:08:20 +0200, Rolf Eike Beer said: So any version checking like I do in the CXXFeatures test (I have compiler version X, the supported features should be ...) is entirely mood for Clang. Great. Well, I don't know what we're really talking about here... but it sounds like

Re: [cmake-developers] Suspicious Clang versions

2013-08-05 Thread Sean McBride
On Mon, 5 Aug 2013 09:44:00 -0400, Brad King said: and local testing we can use __APPLE_CC__ to detect Apple compiler builds. In my own build of open source clang from svn trunk, it seems that __APPLE_CC__ is defined: $ clang -dM -E - /dev/null #define __APPLE_CC__ 5621 So I don't think

Re: [cmake-developers] Suspicious Clang versions

2013-08-05 Thread Rolf Eike Beer
Sean McBride wrote: On Mon, 5 Aug 2013 08:08:20 +0200, Rolf Eike Beer said: So any version checking like I do in the CXXFeatures test (I have compiler version X, the supported features should be ...) is entirely mood for Clang. Great. Well, I don't know what we're really talking about

Re: [cmake-developers] Suspicious Clang versions

2013-08-05 Thread Brad King
On 08/05/2013 11:33 AM, Sean McBride wrote: In my own build of open source clang from svn trunk, it seems that __APPLE_CC__ is defined: $ clang -dM -E - /dev/null #define __APPLE_CC__ 5621 So I don't think that will help. I also see __apple_build_version__ in that output. Searching

Re: [cmake-developers] Suspicious Clang versions

2013-08-05 Thread Brad King
On 08/05/2013 03:28 PM, Brad King wrote: I also see __apple_build_version__ in that output. Searching for it finds that it is used for this purpose in Qt: https://qt.gitorious.org/qt/qtbase/commit/26c7bb25 but seems to be undocumented in general. Will that work? Embarcadero's

Re: [cmake-developers] Suspicious Clang versions

2013-08-05 Thread Rolf Eike Beer
Brad King wrote: On 08/05/2013 02:08 AM, Rolf Eike Beer wrote: s...@rogue-research.com wrote: very confusingly, Apple uses their own version numbering scheme. So that's Apple clang 4.0. It comes with whatever version of Xcode that machine's running (4.4 I think?). any version

Re: [cmake-developers] Suspicious Clang versions

2013-08-04 Thread David Cole
cmake-developers@cmake.org Sent: Sat, Aug 3, 2013 11:05 pm Subject: [cmake-developers] Suspicious Clang versions http://open.cdash.org/testDetails.php?test=201937899build=2986383 (MacOS 10.7) The CXX compiler identification is Clang 4.0.0 I do not believe that. Especially as http

Re: [cmake-developers] Suspicious Clang versions

2013-08-04 Thread sean
Yeah, it's confusing... :( http://open.cdash.org/testDetails.php?test=201937899build=2986383 (MacOS 10.7) The CXX compiler identification is Clang 4.0.0 I do not believe that. Apple has their own fork/branch of clang which they use in Xcode. AFAICT it's not so different from the open

[cmake-developers] Suspicious Clang versions

2013-08-02 Thread Rolf Eike Beer
http://open.cdash.org/testDetails.php?test=201937899build=2986383 (MacOS 10.7) The CXX compiler identification is Clang 4.0.0 I do not believe that. Especially as http://open.cdash.org/testDetails.php?test=201937829build=2986379 (MacOS 10.8) shows 3.4.0. But since even 3.4 does not seem to