[cfe-dev] 'scan-build ./configure' hang

Jonathan Roelofs via cfe-dev cfe-dev at lists.llvm.org
Wed Nov 11 13:46:15 PST 2015



On 11/11/15 2:44 PM, Maarten Hoes wrote:
> Hi,
>
>
> On Wed, Nov 11, 2015 at 10:37 PM, Jonathan Roelofs via cfe-dev
> <cfe-dev at lists.llvm.org <mailto:cfe-dev at lists.llvm.org>> wrote:
>  >
>  > 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).
>  >
>
> Well it that case, ive been doing it wrong for *years* now.
> ;)
>
> I thought the reason for running configure through scan-build, is
> because configure generates the makefiles that contain CC= (and friends)
> that will give you gcc instead of ccc-analyzer if you dont run
> 'scan-build ./configure', so that you can just do :
>
> $ scan-build -o /dir1/dir2 ./configure
> $ scan-build make
>
>
> Of course, I may be wrong.

Oh, yeah, you're right.


Jon

>
>
> - Maarten
>
>

-- 
Jon Roelofs
jonathan at codesourcery.com
CodeSourcery / Mentor Embedded



More information about the cfe-dev mailing list