You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What version of protobuf and what language are you using?
Version: 4.26.0/3.25.3
Language: Ruby
What operating system (Linux, Windows, ...) and version?
This issue is OS independent that it happens on all OS.
What runtime / compiler are you using (e.g., python version or gcc version)
JRuby 9.4.6.0
What did you do?
gem install google-protobuf
What did you expect to see
Gem successfully installed.
What did you see instead?
ERROR: Failed to build gem native extension.
This appears to be a regression from ffi-compiler 1.3.1 which is released today, however the details of this regression is unknown: ffi/ffi-compiler#26
ffi-compiler gem is completely untested according to its maintainer's comment here, so it's not surprising at all that a new release breaks protobuf installation.
@acozzette I think this is probably a good reason to prioritize #15555 to remove ffi-compiler and rake dependency.
ntkme
changed the title
ffi-compiler 1.3.1 breaks google-protobuf installation on JRuby
[Ruby] ffi-compiler 1.3.1 breaks google-protobuf installation on JRuby
Mar 13, 2024
What version of protobuf and what language are you using?
Version: 4.26.0/3.25.3
Language: Ruby
What operating system (Linux, Windows, ...) and version?
This issue is OS independent that it happens on all OS.
What runtime / compiler are you using (e.g., python version or gcc version)
JRuby 9.4.6.0
What did you do?
What did you expect to see
Gem successfully installed.
What did you see instead?
This appears to be a regression from ffi-compiler 1.3.1 which is released today, however the details of this regression is unknown:
ffi/ffi-compiler#26
Anything else we should know about your project / environment
https://github.com/sass-contrib/sass-embedded-host-ruby/actions/runs/8271884102/job/22632613467
The text was updated successfully, but these errors were encountered: