hitstergtd 415af27395 Problem: Coverage option broken with LLVM GCOV ... Solution: This is an issue with the imported Autoconf M4 macro package for standardised code coverage builds, i.e. using --enable-code-coverage. The simplest way that I could find is to add a case statement that checks if the output of running `gcov -version` contains the "LLVM" keyword; if that is true then do not link with LIBGCOV as its neither required nor supported when using the GCOV frontend for LLVM; least not on Mac OS X. The case statement would also be the most portable. Moreover, using the "-version" argument instead of "-v" seems to be the best bet as that is supported by the normal GCOV and LLVM GCOV frontend. Upstream candidate - this solution should be improved by Autoconf M4 macro overlords and applied to the upstream M4 package; I could not find a suitable way to detect if LLVM GCOV is being used, except for the solution herein; this should also work on *BSD too.		2016-05-09 13:27:41 +01:00
..
ax_check_compile_flag.m4	Problem: autoconf-archive m4 macros out of date	2016-05-02 16:12:27 +01:00
ax_code_coverage.m4	Problem: Coverage option broken with LLVM GCOV	2016-05-09 13:27:41 +01:00
ax_cxx_compile_stdcxx_11.m4	Problem: autoconf-archive m4 macros out of date	2016-05-02 16:12:27 +01:00
ax_cxx_compile_stdcxx.m4	Problem: autoconf-archive m4 macros out of date	2016-05-02 16:12:27 +01:00
ax_valgrind_check.m4	Problem: no Makefile target for Valgrind	2016-03-19 21:54:29 +00:00