-
Notifications
You must be signed in to change notification settings - Fork 15.5k
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
Ruby Gem v3.20.0 on arm64 requires >= Ruby 3.1 #9733
Comments
This is an unexpected change from what I'm reading in the changelog as well. |
It was likely caused by #9657 if I had to guess. |
You mean arm64, right? |
yes 🤦♂️ thanks @uhoh-itsmaciek |
I haven't investigated whether there's a reason for this, but: Depends on Ruby Depends on Ruby Depends on Ruby Depends on Ruby So there is not a single version of Ruby which works for all the platforms of 3.20.0 (eg |
It appears this is no longer an issue with newer versions, since the compiled gem version has been removed for ARM64 (and so it now builds things from source again, as before) - and therefore I think this can be closed.
|
What version of protobuf and what language are you using?
Version: 3.20.0
Language: Ruby
What operating system (Linux, Windows, ...) and version?
macOS M1 - ARM64
What runtime / compiler are you using (e.g., python version or gcc version)
Ruby 2.7
What did you do?
bundle install
What did you expect to see
Successful install
What did you see instead?
Make sure you include information that can help us debug (full error message, exception listing, stack trace, logs).
Anything else we should know about your project / environment
I've had a look at the gemspec and the Rakefile and I can't see a reason that the amd64 version requires ruby 3.1. All the other versions of the gem require only ruby 2.5/
For reference, the rubygems entry for
arm64-darwin
: https://rubygems.org/gems/google-protobuf/versions/3.20.0-arm64-darwinfor
x86_64-darwin
: https://rubygems.org/gems/google-protobuf/versions/3.20.0-x86_64-darwinThe text was updated successfully, but these errors were encountered: