-
Notifications
You must be signed in to change notification settings - Fork 25
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
Problem using gem in Ruby 3.2.2 and bundler 2.4.10 #13
Comments
Hi @fragkakis,I encountered the same issue, and I had to manually build the gem to get it to work. You can try following the instructions below; they might help resolve your problem.
❯ gem info levenshtein-ffi
*** LOCAL GEMS ***
levenshtein-ffi (1.1.0)
Author: David Balatero
Homepage: http://github.com/dbalatero/levenshtein-ffi
License: BSD 2-Clause
Installed at: /home/tlvu/.asdf/installs/ruby/2.7.8/lib/ruby/gems/2.7.0
An FFI version of the levenshtein gem. ❯ bundle info levenshtein-ffi
* levenshtein-ffi (1.1.0)
Summary: An FFI version of the levenshtein gem.
Homepage: http://github.com/dbalatero/levenshtein-ffi
Path: /home/tlvu/.asdf/installs/ruby/2.7.8/lib/ruby/gems/2.7.0/gems/levenshtein-ffi-1.1.0
❯ cd /home/tlvu/.asdf/installs/ruby/2.7.8/lib/ruby/gems/2.7.0/gems/levenshtein-ffi-1.1.0
❯ cd ext/levenshtein/ && ruby extconf.rb && make && cd ../.. |
I think this is the underlying cause: rubygems/rubygems#6205 |
And this looks like a proposed fix: #11 |
ruby 3.1.4p223, rubygems 3.4.19, Bundler 2.4.15 also had this issue and solved by re-build the gem as suggested by this comment, thanks! |
When we were on ruby 2.7.7 and bundler 2.3.14
bundle install
produced an.so
file. When we upgraded our project to ruby 3.2.2 and bundler 2.4.10, we had to drop the gem as a dependency because the.so
file is no longer being created. Bundle install works, but when I try to run our unit tests I am getting the error in the end.Is the gem usable with the new versions of ruby and bundler?
The text was updated successfully, but these errors were encountered: