From: Tobias Brunner <tobias@strongswan.org>
Date: Mon, 21 Aug 2017 09:08:59 +0000 (+0200)
Subject: coverage: Use absolute path when removing paths with lcov
X-Git-Tag: 5.6.1dr1~9
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=0d11d7b1109973e72beee40649e1ef3e6377665d;p=thirdparty%2Fstrongswan.git

coverage: Use absolute path when removing paths with lcov

There is a bug in some versions of lcov that causes it to fail writing
to files via relative paths after it issued warnings (e.g. due to
negative counts in the tracefile).
---

diff --git a/Makefile.am b/Makefile.am
index 47e9e8ce65..54b8220502 100644
--- a/Makefile.am
+++ b/Makefile.am
@@ -59,7 +59,7 @@ cov-report:
 		lcov -c -o $(top_builddir)/coverage/coverage.info -d $(top_builddir) \
 			 --rc lcov_branch_coverage=1
 		lcov -r $(top_builddir)/coverage/coverage.info '*/tests/*' '*/suites/*' '/usr*' \
-			 -o $(top_builddir)/coverage/coverage.cleaned.info \
+			 -o $(abs_top_builddir)/coverage/coverage.cleaned.info \
 			 --rc lcov_branch_coverage=1
 		genhtml --num-spaces 4 --legend --branch-coverage --ignore-errors source \
 				-t "$(PACKAGE_STRING)" \