scan-build: Run 'scan-view /var/tmp/portage/sys-cluster/pacemaker-1.1.16/temp/scan-build-2017-07-11-174611-20818-1' to examine bug reports. for d in replace lib mcp attrd pengine cib crmd fencing lrmd tools; do cppcheck -q $d; done /bin/sh: cppcheck: command not found /bin/sh: cppcheck: command not found /bin/sh: cppcheck: command not found /bin/sh: cppcheck: command not found ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.0-desktop-gnome_libressl_20170706-202936 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-6.3.0 * Available Python interpreters, in order of preference: [1] python3.4 [2] python2.7 (fallback) [3] jython2.7 (fallback) java-config: The following VMs are available for generation-2: *) IcedTea JDK 3.4.0 [icedtea-bin-8] Available Java Virtual Machines: [1] icedtea-bin-8 system-vm
Created attachment 483280 [details] emerge-info.txt
Created attachment 483282 [details] emerge-history.txt
Created attachment 483284 [details] environment
Created attachment 483286 [details] etc.portage.tbz2
Created attachment 483288 [details] logs.tbz2
Created attachment 483290 [details] sys-cluster:pacemaker-1.1.16:20170711-154238.log.bz2
Created attachment 483292 [details] temp.tbz2
Confirming: all existing ebuilds contain code calling cppcheck and none pull in cppcheck as a dependency.
PS: I think the call should be patched out.
FWIU, this package has been revived. Please CC treecleaners again if the new 'maintainer' doesn't cope.
I re-checked with latest (and only) version 2.0.5 in Gentoo just now. Even if I rename the cppcheck command, the tests do not fail, the log shows no mention of cppcheck and the Makefile doesn't seem to have any other target depend on target "cppcheck". I am therefore confident that the issue "has fixed itself upstream" in the meantime. Closing as "obsolete", please re-open as needed.
