-
Notifications
You must be signed in to change notification settings - Fork 35
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
Stop suppressing warnings with -Wno-cast-function-type #315
Comments
@aalexand, I changed the node version in the title, based on the nodedir used. Correct me if I switched to the wrong node version. |
@nolanmar511 Ah, thanks, yes it was a mistake. |
The ones originating from our files should be fixed by #318. Most of these we need NAN to address (nodejs/nan#810) |
Can we get a release made with at least the fixes from #318 while waiting for NAN to address the remaining issues? |
Thanks! |
@nolanmar511 The latest released agent still has the deprecation warnings from its compilation - what's the status? |
nodejs/nan#810 has been fixed, but not released since that fix. I asked on that issue for a new release of NAN. |
With latest version of NAN installed, no deprecation warnings appear on master when using 10.12.0. Marking this as fixed. |
@nolanmar511 Are prober logs also free of deprecation warnings now? |
Still seeing the deprecation warnings in prober logs. I think we'd have to do a release. |
Installing the latest version of Closing this. |
Re-opening. I still see warnings in our prober. |
I reproduced an an ubuntu GCE instance. For reference, here are deprecation warnings:
|
Re-purposing this issue to be about removing the suppression of warnings added in #424 . |
Removed from Beta hotlist, since this issue has been re-purposed and original deprecation warnings no longer appear. |
Marking this as fixed since native component is now in pprof module. |
The text was updated successfully, but these errors were encountered: