path: root/build-gluster-org
diff options
authorAmar Tumballi <>2019-06-10 22:58:17 +0530
committerAmar Tumballi <>2019-06-10 22:58:20 +0530
commitcdac43d2eaf40f686a6f2519f4183a6ededbd087 (patch)
tree20bb19e7667a633a7c6c527490001f7e6d552901 /build-gluster-org
parentb428b99db2a2b847d9e6ff4281ea61f4b324c5e9 (diff)
clang: add '-analyze-header' option
Some of the recent analysis of the clang scan report shows that some macros were not considered while analyzing. Specially the LIST_INIT(), causing at least 30+ false positives. This is an effort to see if this option has anything to do with that. Change-Id: I589050eea6088bfe7adffdc7c23a2228f8c71631 Signed-off-by: Amar Tumballi <>
Diffstat (limited to 'build-gluster-org')
1 files changed, 1 insertions, 1 deletions
diff --git a/build-gluster-org/scripts/ b/build-gluster-org/scripts/
index 5574bff..5def953 100644
--- a/build-gluster-org/scripts/
+++ b/build-gluster-org/scripts/
@@ -6,7 +6,7 @@ $MOCK --install rpcgen libtirpc-devel langpacks-en glibc-langpack-en automake au
$MOCK --copyin $WORKSPACE /src
$MOCK --chroot "cd /src && ./"
$MOCK --chroot "cd /src && ./configure CC=clang --enable-gnfs --enable-debug"
-$MOCK --chroot "cd /src && scan-build -o /src/clangScanBuildReports -disable-checker deadcode.DeadStores -v -v --use-cc clang --use-analyzer=/usr/bin/clang make"
+$MOCK --chroot "cd /src && scan-build -o /src/clangScanBuildReports -disable-checker deadcode.DeadStores -v -v -analyze-headers --use-cc clang --use-analyzer=/usr/bin/clang make"
$MOCK --copyout /src/clangScanBuildReports $WORKSPACE/clangScanBuildReports
$MOCK --clean
sudo chown -R jenkins:jenkins clangScanBuildReports