[master] a65aa02 Enable optional lcov support

[Federico Schwindt]

If we inline CODE_COVERAGE_RULES it builds fine in FreeBSD.

Haven't really tested trying to get coverage working there.

Answering your question, this is tied to GCC, yes.

On Thu, Apr 7, 2016 at 10:22 AM, Poul-Henning Kamp <phk at phk.freebsd.dk>
wrote:

> --------
> In message <CABoVN9CQJ9Fwehz7zvMOqSwuNH=
> EcgTyD0EraqmfLD+bBp77FQ at mail.gmail.com>
> , Dridi Boukelmoune writes:
> >On Mon, Apr 4, 2016 at 10:45 PM, Dridi Boukelmoune <dridi at varni.sh>
> wrote:
> >>> Uhm, this seems to only work with GNU-make  ?
> >>
> >> My bad, I assumed OK meant it had been tested. I just installed bmake
> >> on my machine, I'll have a look and see what's tying it to gmake. I'm
> >> getting tired of GNU extensions creeping everywhere :(
> >
> >I had a look at this, and it doesn't look like something that can be
> >fixed in a reasonable amount of time. The conditional logic can be
> >moved from the generated Makefile to the m4/autoconf parts. That
> >whould be make-friendly while still being gmake-only once enabled.
> >
> >Would that be OK?
>
> Have I mentioned how much I hate the entire autocrap thing for
> reducing portability instead of increasing it ?
>
> Does this LCOV stuff even work with LLVM or does it tie you to GCC ?
>
> --
> Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
> phk at FreeBSD.ORG         | TCP/IP since RFC 956
> FreeBSD committer       | BSD since 4.3-tahoe
> Never attribute to malice what can adequately be explained by incompetence.
>
> _______________________________________________
> varnish-commit mailing list
> varnish-commit at varnish-cache.org
> https://www.varnish-cache.org/lists/mailman/listinfo/varnish-commit
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.varnish-cache.org/lists/pipermail/varnish-commit/attachments/20160407/d7b79a66/attachment.html>