[llvm-dev] Will libFuzzer be part of future release binary packages?

[George Karpenkov via llvm-dev]

Yes, I would like that to happen.
Also with the introduction of -fsanitize=fuzzer argument to Clang I think we have to do that.

This is technically easy to do, but for now I think it’s better to see and wait whether we can move
libFuzzer to compiler-rt under a more permissive license, as that might change the library output location.
Hopefully, that should all happen very soon.

There’s also a ticket on bugzilla about libFuzzer missing from Debian LLVM distribution, not sure what happened to that.

> On Jul 21, 2017, at 1:45 PM, Johan Engelen <jbc.engelen at gmail.com> wrote:
> 
> Great!
> For extra motivation: LDC too supports libFuzzer and including it by default in the LLVM binary package (and build process) would help a lot in testing and packaging LDC.
> 
> Cheers,
>   Johan
> 
> 
> On Fri, Jul 21, 2017 at 10:38 PM, Kostya Serebryany <kcc at google.com <mailto:kcc at google.com>> wrote:
> My understanding is that George is working towards this goal. 
> 
> On Fri, Jul 21, 2017 at 1:30 PM, Johan Engelen via llvm-dev <llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org>> wrote:
> Hi all,
>   Will libFuzzer be part of the release pre-built binaries at http://releases.llvm.org/ <http://releases.llvm.org/> in the future?
> 
> Thanks,
>   Johan
> 
> 
> 
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org>
> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev <http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev>
> 
> 
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20170721/d982a712/attachment.html>