Our application is a JRuby application, and something about the way it is configured causes this to occur. I can install god in a Ruby 2.3.3 / Rails 4.2 app without issue. Jruby 9.05 and 9.01 / Rails 3.2 however, gives me the "C extensions" error on OSX and CentOS.
My objective is to automatically start Resque servers in production, and I don't like the other options, so I'm hoping someone can suggest a workaround or configuration option.
Here's the output. It deletes the ./siteconf.*rb on each run and the filename is unique as well:
Mongo:plus jeff$ gem install god
Building native extensions. This could take a while...
ERROR: Error installing god:
ERROR: Failed to build gem native extension.
current directory: /Users/jeff/.rvm/gems/jruby-9.0.5.0@rails3.2god/gems/god-0.13.7/ext/god
/Users/jeff/.rvm/rubies/jruby-9.0.5.0/bin/jruby -r ./siteconf20170905-61042-zgo8dn.rb extconf.rb
NotImplementedError: C extensions are not supported
<top> at /Users/jeff/.rvm/rubies/jruby-9.0.5.0/lib/ruby/stdlib/mkmf.rb:1
require at org/jruby/RubyKernel.java:937
(root) at /Users/jeff/.rvm/rubies/jruby-9.0.5.0/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:1
<top> at extconf.rb:1
extconf failed, exit code 1
Gem files will remain installed in /Users/jeff/.rvm/gems/jruby-9.0.5.0@rails3.2god/gems/god-0.13.7 for inspection.
Results logged to /Users/jeff/.rvm/gems/jruby-9.0.5.0@rails3.2god/extensions/universal-java-1.8/2.2.0/god-0.13.7/gem_make.out
Just stumbled upon this, too, and I think God might have been written with only MRI in mind. Would still be nice, @mojombo, to know whether JRuby is considered in-scope by you or not?
Our application is a JRuby application, and something about the way it is configured causes this to occur. I can install god in a Ruby 2.3.3 / Rails 4.2 app without issue. Jruby 9.05 and 9.01 / Rails 3.2 however, gives me the "C extensions" error on OSX and CentOS.
My objective is to automatically start Resque servers in production, and I don't like the other options, so I'm hoping someone can suggest a workaround or configuration option.
Here's the output. It deletes the ./siteconf.*rb on each run and the filename is unique as well: