New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ossfuzz: Move to C++ for curl_fuzzer. #1851
Conversation
Automake gets confused if you want to use C++ static libraries with C code - basically we need to involve the clang++ linker. The easiest way of achieving this is to rename the C code as C++ code. This gets us a bit further along the path and ought to be compatible with Google's version of clang.
Ok, travis is happy again, and I've verified this works with oss-fuzz. Hopefully we can get this in today or tomorrow. |
Unfortunately, this breaks many of the autobuilds as well as default installations of MinGW and Cygwin because no C++ compiler is installed. I'm not an autoconf expert and don't have access to a computer at the moment, unfortunately - can the part in configure.ac maybe be made conditional on if I want fuzzing somehow? |
Ugh - that's a pain. I don't have access to my computers until Friday afternoon; @bagder; any thoughts? |
The tests for object file/executable file extensions are presumably only done for the first of these macros in the configure file. Bug: #1851 (comment) Reported-by: Marcel Raad
My take at this: #1873 |
The tests for object file/executable file extensions are presumably only done for the first of these macros in the configure file. Bug: #1851 (comment) Reported-by: Marcel Raad Closes #1873
Automake gets confused if you want to use C++ static libraries with C
code - basically we need to involve the clang++ linker. The easiest way
of achieving this is to rename the C code as C++ code. This gets us a
bit further along the path and ought to be compatible with Google's
version of clang.
This is mostly a check to see if travis is happy - if it is, great!