-
-
Notifications
You must be signed in to change notification settings - Fork 85
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
Please update intree copy of libev #220
Comments
@ioquatix can you take care of this? I can provide some instructions (which I should probably write down somewhere better than this issue but):
Not the greatest process. Perhaps we can look at writing a rake task that automates this or something. |
Sure - I did this recently - but is there a newer update? I'll check. |
your patching introduces a bug: ev_backend_poll
and it also complains about:
|
just adding return 0 at the end would make it build but i am almost sure that is not what you want there :) |
tested with 2.5.1. still broken ev_backend_poll:
```
error: no return statement in function returning non-void
[-Werror=return-type]
```
|
Hmmm it looks like issues with libev, if you have a few minutes you can rewrite |
|
Yes those other issues are in upstream libev as well. but the important
thing is the code patched in by you for the extension. the upstream
issues are annoying warnings (and libev has a lot of them) but can be
ignored for now.
|
Yes agreed |
`rb_thread_call_without_gvl` expects return type `void*`. Fixes #220.
Improve compatibility of `ruby_xrealloc`. Fixes #220.
Okay this has been released in v2.5.2. It was live streamed https://youtu.be/YqYYrpvGWo4 In the future please create new issues for bugs like this. |
confirmed. |
the version that you have right now fails for some distros.
https://build.opensuse.org/package/live_build_log/home:darix:apps/rubygem-nio4r/openSUSE_Tumbleweed/x86_64
while our newer libev copy just works
https://build.opensuse.org/package/live_build_log/openSUSE:Factory/libev/standard/x86_64
The text was updated successfully, but these errors were encountered: