Skip to content
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

Sub-process invocations of JRuby with jruby-complete fail in 1.7.21 #3141

rtyler opened this Issue Jul 15, 2015 · 2 comments


None yet
2 participants
Copy link

rtyler commented Jul 15, 2015

Here's a gist with some example output between and 1.7.21 when installing a gem that has a native extension component to it (e.g. thrift 0.9.1)

This is pretty easy to reproduce in jruby-gradle land with the following build.gradle:

buildscript {
    repositories { jcenter() }

    dependencies {
        classpath "com.github.jruby-gradle:jruby-gradle-plugin:0.4.0"

apply plugin: 'com.github.jruby-gradle.base'

jruby {
    defaultVersion = jrubyVersion
    execVersion = jrubyVersion

dependencies {
    gems 'rubygems:thrift:0.9.1'

Then just invoke:

  • Failure: ./gradlew -PjrubyVersion=1.7.21 jrubyPrepare
  • Success: ./gradlew -PjrubyVersion= jrubyPrepare

Looks like something went awry in 1.7.21

@rtyler rtyler added this to the JRuby 1.7.22 milestone Jul 15, 2015


This comment has been minimized.

Copy link

mkristian commented Jul 16, 2015

simpler way to reproduce

$ GEM_HOME=target java -jar maven/jruby-complete/target/jruby-complete-1.7.22-SNAPSHOT.jar -S gem install thrift

Building native extensions.  This could take a while...
ERROR:  Error installing thrift:
    ERROR: Failed to build gem native extension.

    "java -cp :/home/christian/projects/active/jruby/jruby17/maven/jruby-complete/target/jruby-complete-1.7.22-SNAPSHOT.jar org.jruby.Main" -r ./siteconf20150716-27293-r7lex4.rb extconf.rb
/bin/sh: 1: java -cp :/home/christian/projects/active/jruby/jruby17/maven/jruby-complete/target/jruby-complete-1.7.22-SNAPSHOT.jar org.jruby.Main: not found

extconf failed, uncaught signal 127

Gem files will remain installed in /home/christian/projects/active/jruby/jruby17/target/gems/thrift- for inspection.
Results logged to /home/christian/projects/active/jruby/jruby17/target/extensions/universal-java-1.7/1.9/thrift-

This comment has been minimized.

Copy link

mkristian commented Jul 24, 2015

fixed via 917d0e7

@mkristian mkristian closed this Jul 24, 2015

headius added a commit that referenced this issue Feb 24, 2016

Disable this. thrift is a native gem. Don't know why we try it.
See #3141 and 917d0e7 for the bug that prompted this. It now fails
with a different reason, perhaps due to chdir being used during
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.