1. 09 May, 2016 1 commit
    • hitstergtd's avatar
      Problem: Coverage option broken with LLVM GCOV · 415af273
      hitstergtd authored
      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.
      415af273
  2. 08 May, 2016 4 commits
  3. 06 May, 2016 5 commits
  4. 05 May, 2016 7 commits
  5. 04 May, 2016 15 commits
  6. 03 May, 2016 8 commits