[cfe-dev] Using clang/LLVM components in conventional apps?

[Alexei Svitkine]

Hmm - clang seems to be having trouble compiling Mac OS X headers:

In file included from
/Developer/SDKs/MacOSX10.4u.sdk/System/Library/Frameworks/CoreFoundation.framework/Headers/CoreFoundation.h:12,
                 from
/Developer/SDKs/MacOSX10.4u.sdk/System/Library/Frameworks/CoreServices.framework/Frameworks/CarbonCore.framework/Headers/CarbonCore.h:20,
                 from
/Developer/SDKs/MacOSX10.4u.sdk/System/Library/Frameworks/CoreServices.framework/Headers/CoreServices.h:24,
                 from
/Developer/SDKs/MacOSX10.4u.sdk/System/Library/Frameworks/Carbon.framework/Headers/Carbon.h:24,
                 from
/Users/shadowknight/Projects/myth2/merged-1.6/Myth2Code/cseries/final_carbon.h:15:
/Developer/SDKs/MacOSX10.4u.sdk/usr/include/stdarg.h:4:25: error:
stdarg.h: No such file or directory
In file included from
/Developer/SDKs/MacOSX10.4u.sdk/System/Library/Frameworks/CoreFoundation.framework/Headers/CoreFoundation.h:16,
                 from
/Developer/SDKs/MacOSX10.4u.sdk/System/Library/Frameworks/CoreServices.framework/Frameworks/CarbonCore.framework/Headers/CarbonCore.h:20,
                 from
/Developer/SDKs/MacOSX10.4u.sdk/System/Library/Frameworks/CoreServices.framework/Headers/CoreServices.h:24,
                 from
/Developer/SDKs/MacOSX10.4u.sdk/System/Library/Frameworks/Carbon.framework/Headers/Carbon.h:24,
                 from
/Users/shadowknight/Projects/myth2/merged-1.6/Myth2Code/cseries/final_carbon.h:15:
/Developer/SDKs/MacOSX10.4u.sdk/usr/include/float.h:8:24: error:
float.h: No such file or directory
In file included from
/Developer/SDKs/MacOSX10.4u.sdk/System/Library/Frameworks/CoreServices.framework/Frameworks/CarbonCore.framework/Headers/DriverServices.h:32,
                 from
/Developer/SDKs/MacOSX10.4u.sdk/System/Library/Frameworks/CoreServices.framework/Frameworks/CarbonCore.framework/Headers/CarbonCore.h:125,
                 from
/Developer/SDKs/MacOSX10.4u.sdk/System/Library/Frameworks/CoreServices.framework/Headers/CoreServices.h:24,
                 from
/Developer/SDKs/MacOSX10.4u.sdk/System/Library/Frameworks/Carbon.framework/Headers/Carbon.h:24,
                 from
/Users/shadowknight/Projects/myth2/merged-1.6/Myth2Code/cseries/final_carbon.h:15:
/Developer/SDKs/MacOSX10.4u.sdk/System/Library/Frameworks/CoreServices.framework/Frameworks/CarbonCore.framework/Headers/MachineExceptions.h:29:23:
error: xmmintrin.h: No such file or directory
In file included from
/Developer/SDKs/MacOSX10.4u.sdk/System/Library/Frameworks/CoreServices.framework/Frameworks/CarbonCore.framework/Headers/DriverServices.h:32,
                 from
/Developer/SDKs/MacOSX10.4u.sdk/System/Library/Frameworks/CoreServices.framework/Frameworks/CarbonCore.framework/Headers/CarbonCore.h:125,
                 from
/Developer/SDKs/MacOSX10.4u.sdk/System/Library/Frameworks/CoreServices.framework/Headers/CoreServices.h:24,
                 from
/Developer/SDKs/MacOSX10.4u.sdk/System/Library/Frameworks/Carbon.framework/Headers/Carbon.h:24,
                 from
/Users/shadowknight/Projects/myth2/merged-1.6/Myth2Code/cseries/final_carbon.h:15:
/Developer/SDKs/MacOSX10.4u.sdk/System/Library/Frameworks/CoreServices.framework/Frameworks/CarbonCore.framework/Headers/MachineExceptions.h:254:
error: '__m128' does not name a type
/Developer/SDKs/MacOSX10.4u.sdk/System/Library/Frameworks/CoreServices.framework/Frameworks/CarbonCore.framework/Headers/MachineExceptions.h:255:
error: '__m128i' does not name a type
/Developer/SDKs/MacOSX10.4u.sdk/System/Library/Frameworks/CoreServices.framework/Frameworks/CarbonCore.framework/Headers/MachineExceptions.h:256:
error: '__m128d' does not name a type

Are these known issues? Is it possible to pass some flags or something
to clang to work-around these?

-Alexei

On Fri, Jun 26, 2009 at 2:22 PM, Chris Lattner<clattner at apple.com> wrote:
> On Jun 26, 2009, at 11:20 AM, Alexei Svitkine wrote:
>>
>> On a similar note, I was recently wondering...
>>
>> How would one make clang appear as one of the compilers in the
>> drop-down GUI in Xcode?
>>
>> Is there some information on this somewhere?
>
> Oh, another less horrible hack is to add a custom build setting to the build
> setting inspector of CC = /path/to/clang.
>
> -Chris
>
>>
>> -Alexei
>>
>> On Fri, Jun 26, 2009 at 11:39 AM, Dallman, John<john.dallman at siemens.com>
>> wrote:
>>>
>>> Douglas Gregor [mailto:dgregor at apple.com] wrote:
>>>
>>>> Clang produces conventional .o files that are 100% binary-compatible
>>>> with GCC.
>>>
>>> Splendid! I'll give it a try when we upgrade our build standard to Mac
>>> OS X 10.6 and a newer Xcode than 3.0. Currently, we have stable
>>> production
>>> on those tools, and we can't just change without giving customers
>>> notice.
>>>
>>> --
>>> John Dallman
>>>
>>> _______________________________________________
>>> cfe-dev mailing list
>>> cfe-dev at cs.uiuc.edu
>>> http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev
>>>
>> _______________________________________________
>> cfe-dev mailing list
>> cfe-dev at cs.uiuc.edu
>> http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev
>
>