[llvm-bugs] [Bug 25502] New: 'scan-build ./configure' loops on building 'conftest1.c/conftest2.c'

[via llvm-bugs]

https://llvm.org/bugs/show_bug.cgi?id=25502

            Bug ID: 25502
           Summary: 'scan-build ./configure' loops on building
                    'conftest1.c/conftest2.c'
           Product: clang
           Version: trunk
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P
         Component: Static Analyzer
          Assignee: kremenek at apple.com
          Reporter: hoes.maarten at gmail.com
                CC: llvm-bugs at lists.llvm.org
    Classification: Unclassified

Created attachment 15271
  --> https://llvm.org/bugs/attachment.cgi?id=15271&action=edit
The 'conftest1.c' and 'conftest2.c' ./configure testcases

I'm trying to analyze a certain project [1] with the clang-analyzer. But at a
certain step [2] during 'scan-build ./configure', the command appears to loop.
This step is trying to compile 2 small C testcases, 'conftest1.c' and
'conftest2.c' (which Ive included in the attachment), and the executed
commandline is this :

/bin/sh ./libtool --mode=compile /usr/local/bin/../libexec/ccc-analyzer
conftest1.c -c -o conftest1.lo

Running this on the command line gives me endless lines of this :

Waiting for -c.o.lock to be removed
Waiting for -c.o.lock to be removed
Waiting for -c.o.lock to be removed

If I just run './configure' without scan-build, the configure finishes quite
fast and as expected. I'm running a recent svn version (r252789) of
llvm/clang/scan-build on Fedora 23.


[1]
Hyperion
https://github.com/hercules-390/hyperion

[2]
checking whether getopt wrapper kludge is necessary...

-- 
You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20151112/7b36a4a4/attachment.html>