<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Hi Michael,<div><br></div><div>Sorry for the late reply, it took me a while to reproduce this.</div><div><br></div><div>I successfully reproduced this on Ubuntu (project wouldn't compile under OSX). It looks like a problem with the ccc-analyzer script. I filed <a href="http://llvm.org/bugs/show_bug.cgi?id=8070">Bug 8070</a></div><div><br></div><div>Thanks for reporting!</div><div><br></div><div>Tom</div><div><br><div><div>On 01/09/2010, at 6:47 PM, Michael Blumenkrantz wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div>On Wed, 1 Sep 2010 18:34:40 -0700<br>Ted Kremenek <<a href="mailto:kremenek@apple.com">kremenek@apple.com</a>> wrote:<br><br><blockquote type="cite">Hi Michael,<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">From the error diagnostics it appears that they are coming from Clang when<br></blockquote><blockquote type="cite">httpconnection.c is compiled. I know you said that GCC is being used as the<br></blockquote><blockquote type="cite">compiler, but that doesn't seem to be the case.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">BTW, are you doing a parallel build? It appears that url.c is analyzed<br></blockquote><blockquote type="cite">before httpconnection.c, so it is difficult to tell from the log what is<br></blockquote><blockquote type="cite">going on.<br></blockquote><blockquote type="cite"><br></blockquote>Yes, -j2.<br><blockquote type="cite">FWIW, all ccc-analyzer does is directly forward the command line arguments to<br></blockquote><blockquote type="cite">your compiler (e.g., gcc), and then calls clang with various analyzer comment<br></blockquote><blockquote type="cite">line options. If the analyzer fails, however, that shouldn't cause the build<br></blockquote><blockquote type="cite">to fail. The only reason that ccc-analyzer returns an error code is if the<br></blockquote><blockquote type="cite">compiler it called returned an error code.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Have you tried building your project with Clang? (not using scan-build). I<br></blockquote><blockquote type="cite">suspect that you'll see the same errors, and if so that will at least confirm<br></blockquote><blockquote type="cite">that the build is failing because clang is being used for compilation.<br></blockquote><blockquote type="cite"><br></blockquote>The project compiles fine with both gcc and clang, but fails when using<br>scan-build. You can easily check the code out from<br><a href="http://svn.zentific.com/trunk/Zentific-console/shellinabox">http://svn.zentific.com/trunk/Zentific-console/shellinabox</a> and test this<br>yourself.<br><blockquote type="cite">Also, if clang is indeed being used to build your project, I'm not certain<br></blockquote><blockquote type="cite">why scan-build is using clang to actually build your project unless...<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"> (a) the 'gcc' in your path is a symlink to clang<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">or<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"> (b) the environment variable CCC_CC is set to 'clang'<br></blockquote>I don't remember which cc I was using in the log that I sent just now, but<br>neither compiler is able to finish a build when using scan-build. Required<br>functions that are detected when not using scan-build are no longer detected<br>when using scan-build.<br><blockquote type="cite"><br></blockquote><blockquote type="cite">On Aug 31, 2010, at 9:41 PM, Michael Blumenkrantz wrote:<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><blockquote type="cite">Attached are the output for running configure and make with<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">CCC_ANALYZER_VERBOSE set (log.txt) as well as the config.log file. For<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">whatever reason, when using scan-build it seems to be unable to compile<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">using certain headers.<br></blockquote></blockquote><blockquote type="cite"><br></blockquote>Checking out the code and testing this yourselves will likely be the fastest<br>way to solve this, unless it is somehow unique to my system.<br><br>-- <br>Mike Blumenkrantz<br>Zentific: Our boolean values are huge.<br></div></blockquote></div><br></div></body></html>