search

knu / ruby-digest-whirlpool

Ruby interface to the Whirlpool message digest algorithm
Other
1 stars 7 forks source link

gem install fails with ruby 2.7.2 #2

Open ghost opened 3 years ago

ghost commented 3 years ago

Hello, I have problem with this gem + ruby 2.7.2:

[13:31:19] xspaniki:project457 git:(upgrade-ruby-to-2.7.2*) $ gem install digest-whirlpool
Building native extensions. This could take a while...
ERROR:  Error installing digest-whirlpool:
    ERROR: Failed to build gem native extension.

    current directory: /Users/xspaniki/.rvm/gems/ruby-2.7.2/gems/digest-whirlpool-1.0.3/ext/digest/whirlpool
/Users/xspaniki/.rvm/rubies/ruby-2.7.2/bin/ruby -I /Users/xspaniki/.rvm/rubies/ruby-2.7.2/lib/ruby/2.7.0 -r ./siteconf20201110-10852-1xgz174.rb extconf.rb
checking for ruby/digest.h... yes
creating Makefile

current directory: /Users/xspaniki/.rvm/gems/ruby-2.7.2/gems/digest-whirlpool-1.0.3/ext/digest/whirlpool
make "DESTDIR=" clean

current directory: /Users/xspaniki/.rvm/gems/ruby-2.7.2/gems/digest-whirlpool-1.0.3/ext/digest/whirlpool
make "DESTDIR="
compiling whirlpool-algorithm.c
make: *** No rule to make target `/Users/xspaniki/.rvm/rubies/ruby-2.7.2/include/ruby-2.7.0/digest.h', needed by `whirlpool.o'.  Stop.

make failed, exit code 2

Gem files will remain installed in /Users/xspaniki/.rvm/gems/ruby-2.7.2/gems/digest-whirlpool-1.0.3 for inspection.
Results logged to /Users/xspaniki/.rvm/gems/ruby-2.7.2/extensions/x86_64-darwin-19/2.7.0/digest-whirlpool-1.0.3/gem_make.out
borfd commented 2 years ago

Any luck solving this issue?

borfd commented 2 years ago

Feel free to use my fork which has been updated to work with Ruby 3 :) https://github.com/borfd/ruby-digest-whirlpool

gtk2105 commented 1 year ago

Feel free to use my fork which has been updated to work with Ruby 3 :) https://github.com/borfd/ruby-digest-whirlpool

Hi borfd,

Are you still using SecGen?

This seems to continue with issues as the Ruby versions increase. I have found that both digest-sha3 & digest-whirlpool depends on Ruby 2.2.

Was your solution to simply fork the specific repositories and change the gemspec file, or is there more to it than that?

I look forward to your response.