-
Notifications
You must be signed in to change notification settings - Fork 16
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
Launcher fails with "execv failed: Permission denied (13)" #44
Comments
Debugging this with @headius, it looks like there are two errors. First, my I'll fix this on my machine, but it's probably worth making the launcher a bit more resilient. If nothing else, it could present the user with a neater error message. |
The simple fix will be to check that the |
Have a similar issue after installing JRuby with It will be great to have the error message more specific and friendly to point at the issue. |
@mrnoname1000 Maybe we can make the |
Just occurred to me that this is an issue with the native version of jruby-launcher, not the shell script. We have an improvement for the latter from @mrnoname1000 in jruby/jruby#8648 but the native launcher will need a similar fix (plus a ton of updates for recent shell launcher updates). |
I recently installed JRuby 9.3.1.0 using ruby-build. The ruby-build recipe will install the jruby-launcher gem, which will replace bin/jruby in the distribution. When I try to run JRuby, I see the following error:
If I fetch the JRuby tarball and run it locally with the original bin/jruby, everything works. I've narrowed the issue down to the replaced launcher from jruby-launcher. Moreover, I've discovered I only get the failure when the
JAVA_HOME
env var is not set. With other Java applications, that isn't an issue asjava
is available on thePATH
.Currently, my
java
command is coming from Homebrew for Linux:If I set my
JAVA_HOME
env var to/home/linuxbrew/.linuxbrew/Cellar/openjdk/17
the launcher begins working.Here is the strace output when trying to start the launcher:
This looks like a similar situation to #31.
The text was updated successfully, but these errors were encountered: