-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
CLN/BUILD: Fix clang warnings on build #5385
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
Comments
|
Also, klib may create unused functions because of macros... |
btw - you can see what the build warnings are on Travis too (just expand the build part of the build summary) |
@jreback, numpy is moving on, should we put effort into moving pandas into 1.7 cleanliness? |
I have no idea.....scipy/numpy builds are not clean themselves....does it bother anyone? |
aesthetically? a little bit. there are increasingly more warnings related |
would take someone whom is more familiar with the build process and some time |
so we prob want to have this as an option, but just passing What we could do is have an option to turn this on/off (default on). any thoughts |
If we are not already, we should definitely set |
@wesm that looks like a nice compromise (between using |
I think this can be closed. Numpy/cython are discussing making the deprecated-API warnings suppressable. Other than that there’s not much else to be done. |
Here's the output from the current master. I could try to clean some of the warnings up someday if there's any interest; a decent excuse to look through the source code.
A lot of the warnings look similar:
What do things look like with gcc (and whatever windows uses)?
The text was updated successfully, but these errors were encountered: