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?
to your account
The text was updated successfully, but these errors were encountered:
Sorry, something went wrong.
--use-valgrind is supported in e34f873. Maybe it would be simpler just to allow arbitrary arguments. The HTTP API itself works with arguments.
Environment variables work as well. I just added arbitrary arguments as well, for Linux.
Windows is still a TODO.
OK, implemented for windows as well.
How about -fno-common
I'm also curious about how to pass e.g. -fno-common to R CMD check, as it's a required flag for gcc10 compliance.
R CMD check
@ekalosak That's not a flag for R CMD check. If is a compiler flag, so you can (temporarily) put it in your package's Makevars file.
@gaborcsardi thank you for your quick response.
For others who are interested, the following adds -fno-common to the CFLAGS in a temporary Makevars - useful for running checks on code with native routine bindings.
"CFLAGS"="-Wall -pedantic -fdiagnostics-color=always -fno-common"
Successfully merging a pull request may close this issue.