[PATCH] D20741: [LibFuzzer] Fix weak linking issues building tests under OSX.

[Mehdi Amini via llvm-commits]

Any reason *not* to change libFuzzer to avoid that?
The original intention of the code in libFuzzer (according to the comment) was having them "weak_external". Having to modify the user linker flag is not nice.



> On May 31, 2016, at 3:06 PM, Mike Aizatsky <aizatsky at google.com> wrote:
> 
> aizatsky added a comment.
> 
> I solved this in chromium tree by specifying additional linker arguments:
> 
>  "-Wl,-U,_LLVMFuzzerCustomMutator",
>  "-Wl,-U,_LLVMFuzzerInitialize",
> 
> https://code.google.com/p/chromium/codesearch#chromium/src/testing/libfuzzer/BUILD.gn&l=29
> 
> Is there a reason we shouldn't do the same here without changing libfuzzer code?