[cfe-dev] scan-build failure

[Tom Care]

Neither can GCC, it would seem. Have you tried building without scan-build?

The errors about isnan and strcasestr in your original post don't look like clang errors.

Tom

On Aug 31, 2010, at 6:33 PM, Michael Blumenkrantz wrote:

> On Mon, 30 Aug 2010 13:11:04 -0700
> Ted Kremenek <kremenek at apple.com> wrote:
> 
>> scan-build is not smart enough to know what compiler your build intended to
>> use.  It defaults to assuming 'gcc', since that is still the standard
>> compiler used on most systems.
>> 
>> To correct this, check out the --use-cc option to scan-build
>> 
>> --use-cc [compiler path]   - By default, scan-build uses 'gcc' to compile
>> and link --use-cc=[compiler path]     your C and Objective-C code. Use this
>> option to specify an alternate compiler.
>> 
>> --use-c++ [compiler path]  - By default, scan-build uses 'g++' to compile
>> and link --use-c++=[compiler path]    your C++ and Objective-C++ code. Use
>> this option to specify an alternate compiler.
>> 
>> 
>> 
>> On Aug 30, 2010, at 1:07 PM, Michael Blumenkrantz wrote:
>> 
>>> No, I was just assuming it would default to using clang?
>> 
> No, specifying --use-cc to set clang gives the same result so I guess it
> correctly sets clang for scan-build.  clang cannot compile this project.
> 
> -- 
> Mike Blumenkrantz
> Zentific: Our boolean values are huge.
> _______________________________________________
> cfe-dev mailing list
> cfe-dev at cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev