-
Notifications
You must be signed in to change notification settings - Fork 26
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
Error installing gem in MacOS M1 #34
Comments
Hello, is this still an issue for you? I'm on an M1 as well and haven't had any installation problems. |
Installing 0.0.8 and 0.0.9 on Ubuntu 20.04.6 LTS (Focal Fossa) Same issue |
Same issue here. Resolved on ubuntu by doing apt-get install clang libclang-dev |
I want to help resolve this, but there seem to be two problems here:
I have a fairly good idea of what's going on: the gem is trying to manually compile on your system(s), your system doesn't have the proper build tools to compile it (eg., No one should have needed to compile the gem at all. So, first I would ask, for the Ubuntu users:
|
I think the problem here is that there is different Ruby version constraints on the pre-compiled versions of the gem. For 0.0.10 without precompile the constraint is >= 3.1.0 which means it's only available for Ruby 3.2.x versions. Trying on a docker VM with bundle platform of aarch64-linux I can install with Ruby 3.2.4:
whereas with Ruby 3.3 and 3.4 it tries to install with native extensions. I expect the issue is in this line: Line 24 in 020781a
Where I think you may want to omit the ruby-version or comma separate all supported ones |
To be sure, that line is a problem, yes. But, that script was added only for the 0.0.10 release; the reports before my comment were about 0.0.8 and 0.0.9. (There’s actually also separate problem with the build for 3.3.5+ and 3.4 (oxidize-rb/rb-sys#475) that I’m keeping track of. I incorrectly hardcoded this to 3.2 after being unable to build with 3.3 and 3.4.) |
Sure, sorry about not direct relation. Would you like a fresh issue created for the 3.2 builds? |
No, my curse is that I’m fully aware of every problem 😆 My plan was to wait for the build issues to resolve, push a 0.0.11, and then close this issue. I mentioned earlier that I had an M1 with no issues; subsequent comments were about Ubuntu. I’ll do a better job looking at all the artifacts built for the 0.0.11 gem before pushing the release, but ultimately the problem is the same: for some reason, for some architecture types, the native gem is not being compiled as part of the packaging. No one should need Rust tooling installed to use this gem: that’s the core problem that I intend to look into and fix. It’s just been exacerbated by this 3.3.5+ issue. |
I'm fairly certain this has been fixed as of 0.0.11, for both macOS and Linux. Please try it out. We can reopen the issue if it didn't work. |
The text was updated successfully, but these errors were encountered: