Open mockdeep opened 4 years ago
Having a similar? issue on Windows 10. Note that this is only for v 1.5.4, I am able to successfully install v 1.5.3.
Fetching jaro_winkler 1.5.4
Installing jaro_winkler 1.5.4 with native extensions
Gem::Ext::BuildError: ERROR: Failed to build gem native extension.
current directory:
C:/Ruby26-x64/lib/ruby/gems/2.6.0/gems/jaro_winkler-1.5.4/ext/jaro_winkler
C:/Ruby26-x64/bin/ruby.exe -I C:/Ruby26-x64/lib/ruby/2.6.0 -r
./siteconf20200202-23604-2wsc9q.rb extconf.rb
creating Makefile
current directory:
C:/Ruby26-x64/lib/ruby/gems/2.6.0/gems/jaro_winkler-1.5.4/ext/jaro_winkler
make "DESTDIR=" clean
current directory:
C:/Ruby26-x64/lib/ruby/gems/2.6.0/gems/jaro_winkler-1.5.4/ext/jaro_winkler
make "DESTDIR="
generating jaro_winkler_ext-x64-mingw32.def
compiling adj_matrix.c
compiling codepoints.c
compiling jaro.c
compiling jaro_winkler.c
linking shared-object jaro_winkler/jaro_winkler_ext.so
current directory:
C:/Ruby26-x64/lib/ruby/gems/2.6.0/gems/jaro_winkler-1.5.4/ext/jaro_winkler
make "DESTDIR=" install
/usr/bin/install -c -m 0755 jaro_winkler_ext.so
./.gem.20200202-23604-14dbh3e/jaro_winkler
Permission denied @ apply2files -
C:/Ruby26-x64/lib/ruby/gems/2.6.0/gems/jaro_winkler-1.5.4/lib/jaro_winkler/jaro_winkler_ext.so
Gem files will remain installed in
C:/Ruby26-x64/lib/ruby/gems/2.6.0/gems/jaro_winkler-1.5.4 for inspection.
Results logged to
C:/Ruby26-x64/lib/ruby/gems/2.6.0/extensions/x64-mingw32/2.6.0/jaro_winkler-1.5.4/gem_make.out
An error occurred while installing jaro_winkler (1.5.4), and Bundler cannot
continue.
Make sure that `gem install jaro_winkler -v '1.5.4' --source
'https://rubygems.org/'` succeeds before bundling.
@mockdeep @tyjet
Puma uses RuboCop in its CI, which uses jaro_winkler. You might have a look at a workflow I just did a PR for there, which has the most recent actions that are best used with Ruby:
Thanks for the recommendation @MSP-Greg. For now we disabled installation of rubocop in windows. Do you know what exactly you did to get it installing correctly?
@mockdeep
Well, you said 'we', so I looked to see who we might be. Is this for RMagick? I'll get there, probably tomorrow.
Do you know what exactly you did to get it installing correctly?
Simply put, connected 'devkit'.
What I think you need to do there is install Ruby with the following step:
- name: setup Ruby, gcc, install MSYS2 imagemagick
uses: MSP-Greg/actions-ruby@v1
with:
base: update
mingw: imagemagick
ruby-version: ${{ matrix.ruby }}
Until it's working, start with Ruby >= 2.4
@MSP-Greg Yeah, on RMagick. If you're game to get it working for us, it would be much appreciated. Otherwise, I'll try poking around in the near future. I think we had devkit
when it was on TravisCI, but for some reason it didn't work for us when transitioning to Github Actions.
@mockdeep
Re Actions, depending on how one loads Rubies, devkit
may need to be required, and PATH may need to be cleaned up...
See https://github.com/rmagick/rmagick/pull/1042.
quoting from that PR:
@mockdeep
Summing up re Actions, Windows, and extension gems:
One must 'activate' MSYS2 some way or another, whether with a Ruby/Windows specific action, or in one's workflow steps.
At present, Actions has an embedded MYS2 install in all three of its installed Ruby builds, The issue is that these installs need updating, and that can be tricky, especially if one is using a Ruby that isn't one of the current releases, ie. 2.5.7, 2.6.5, or 2.7.0. The MSYS2 issue should have been dealt with in the Actions beta, but...
I think that sums it up. Fell free to close unless you feel this is a jaro_winkler issue. I hate seeing "can't on Windows" issues...
I'm trying to install this gem in our Github Action using the
windows-latest
OS. Unfortunately, I'm getting the error below. I've seen it succeed in some cases, though, so it doesn't seem to be failing consistently.