<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Nov 11, 2015, at 1:37 PM, Jonathan Roelofs via cfe-dev <<a href="mailto:cfe-dev@lists.llvm.org" class="">cfe-dev@lists.llvm.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><br style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><br style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><span style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">On 11/11/15 2:28 PM, Craig, Ben via cfe-dev wrote:</span><br style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><blockquote type="cite" style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">I usually run 'top' in another console. Often, you will find an<br class="">instance of clang running the analyzer. It is usually taking a fair<br class="">amount of CPU and memory.<br class=""><br class="">If this is the case, then you may be able to look at the command line to<br class="">see which part of the configure is causing the slow build.<br class=""><br class="">On 11/11/2015 3:18 PM, Maarten Hoes via cfe-dev wrote:<br class=""><blockquote type="cite" class="">Hi,<br class=""><br class=""><br class="">I'm trying to analyze a certain project [1] with the clang-analyzer.<br class="">But at a certain step [2] during 'scan-build ./configure', the command<br class="">appears to hang (or at least perform so slowly that it appears to<br class="">hang). If I just run './configure' without scan-build, the configure<br class="">finishes quite fast and as expected. I'm running the latest svn<br class="">version (r252789) of llvm/clang/scan-build on Fedora 23.<br class=""><br class="">I aborted the scan-build and took a look at 'config.log' but must<br class="">admit I'm not quite sure what to look for.<br class=""><br class="">Any and all help to figure out what is going on here, and help fix it,<br class="">is appreciated.<br class=""></blockquote></blockquote><br style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><span style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">I think you ought to be running scan-build on the resulting makefiles, not on configure itself (unless you intend to analyze the code that configure uses to feature-test the compiler).</span><br style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""></div></blockquote><div><br class=""></div><div>It is sometimes important to run scan-build on ./configure as well because configure often generates Makefiles that have paths that are hard-wired to the compiler, which scan-build interposes. There are more details about this at <<a href="http://clang-analyzer.llvm.org/scan-build.html#recommended_autoconf" class="">http://clang-analyzer.llvm.org/scan-build.html#recommended_autoconf</a>>.</div><div><br class=""></div><div>Devin</div></div></body></html>