-
-
Notifications
You must be signed in to change notification settings - Fork 83
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
Building native gem extension nio4r fails on mac OS High Sierra due to integer precision / division by zero #178
Comments
Hi there, The issues you pointed out regarding casts to different integer sizes are just warnings. They are not the actual culprit. The actual culprit is this (and a few other things):
Something (certainly looks like Postgres) installed a I think (temporarily) removing the file should resolve the issue. extconf.rb could be updated to look for e.g. |
Hi Tony, Thanks for replying so quickly to my issue on Christmas! There was indeed an old Merry Christmas! Cheers, |
"port.h" is a pretty generic name, and apparently has caused nio4r to fail to build in practice. Before trying to use it, make sure it contains the types we expect (for Solaris I/O completion ports)
ext/nio4r/extconf.rb: check for port_event_t in port.h (fixes #178)
I'm trying to install the current Rails version on my Mac running High Sierra v10.13.2 but whatever I try, it always fails while building the native gem extensions nio4r.
I'm sure there's something wrong with my system / environment but I can't get my head around the error messages as I'm not really a C developer.
I'm on Ruby 2.4.3 but tried several other versions like 2.5.0, 2.4.0., 2.3.0 via RVM as well. I've found a lot on StackOverflow, etc. around this like missing developer tools and so on, but nothing seems to apply to my situation. Depending on the Ruby version it either fails with integer precision with Ruby 2.4.x or with a division by zero with Ruby 2.5.0.
Here's the error message for Ruby 2.4.3:
And here is the error message for Ruby 2.5.0:
The text was updated successfully, but these errors were encountered: