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
I have an app that uses ruby 2.0(it's actually jruby, running with compatibility to Ruby 2.0), but I see that picky works with only 1.9. And I am getting errors trying to install it. Are there any plans to update Picky to work with 2.0 and up?
The text was updated successfully, but these errors were encountered:
Hi @tehandyb! :) Thanks for the issue! It's already running on 2.3.3 on https://cocoapods.org, so I assume the issues may lie with JRuby. What are the errors?
Hey thanks for the response! I'm using JRuby 1.7.26 with RVM and the error message when I do gem install picky is:
Building native extensions. This could take a while...
ERROR: Error installing picky:
ERROR: Failed to build gem native extension.
/Users/andrewblowe/.rvm/rubies/jruby-1.7.26/bin/jruby -r ./siteconf20170623-72139-14zpzji.rb extconf.rb
Compiling on Ruby 1.9.3 with CC set to cc.
NotImplementedError: C extension support is not enabled. Pass -Xcext.enabled=true to JRuby or set JRUBY_OPTS.
(root) at /Users/andrewblowe/.rvm/rubies/jruby-1.7.26/lib/ruby/shared/mkmf.rb:8
require at org/jruby/RubyKernel.java:1040
(root) at /Users/andrewblowe/.rvm/rubies/jruby-1.7.26/lib/ruby/shared/rubygems/core_ext/kernel_require.rb:1
(root) at extconf.rb:13
extconf failed, uncaught signal 1
Gem files will remain installed in /Users/andrewblowe/.rvm/gems/jruby-1.7.26/gems/picky-4.31.3 for inspection.
Results logged to /Users/andrewblowe/.rvm/gems/jruby-1.7.26/extensions/universal-java-1.8/1.9/picky-4.31.3/gem_make.out
I also tried to set C extension support in my Jruby config to no avail.
I have an app that uses ruby 2.0(it's actually jruby, running with compatibility to Ruby 2.0), but I see that picky works with only 1.9. And I am getting errors trying to install it. Are there any plans to update Picky to work with 2.0 and up?
The text was updated successfully, but these errors were encountered: