Open AndyObtiva opened 4 years ago
I assume you guys are very busy, so I’m gonna take a look at jruby’s code myself when I get a chance to see if I can get this working.
My goal behind it is to provide unified instructions for setting up JRuby and Glimmer on Mac, Linux, and Windows via RVM. Still, there are many other options on Windows, I’m aware of that (e.g. chocolatey and uru). So, I’m not stuck in any way.
Cheers.
@AndyObtiva - I don't use Cygwin but is Cygwin a must in your mind? I have decent instructions for installing JRuby on WIndows on my blog at https://notepad.onghu.com/tags/#JRuby and I recommend using pik for switching between Rubies, including JRuby. Would that help in your case?
(Also, happy to help you try something on Windows if you want)
I am wondering if this issue is really relevant anymore. Yes, there are still folks out there using Cygwin but I would expect that most of them have already moved on to WSL for their unix-on-Windows needs. We still support Cygwin and I will take a brief look at this but maybe it is time to start saying goodbye.
So it seems the problems here are all related to building native libraries. I can't see exactly why these builds fail from this output.
RVM by default will try to install the jruby-launcher gem, which builds a native jruby
executable to avoid the bash script version. Normally this is not needed for the Windows install, since we ship a jruby.exe
in the distribution. We also do not support installing the gem on Windows since it is not set up for Windows build environments. In the future the gem will just ship prebuilt binaries for all supported platforms.
The gem-wrappers gem has an extension build but it appears to just be faking out the system to regenerate the wrapper scripts, I think? The fact that it fails tells me that basic build tools may not be set up in your environment, since it generates a dummy Makefile
but does not actually build any native code.
And I think the rubygems-bundler failure is caused by the aforementioned wrapper generator being hooked into the install process but failing to work.
I do not know the purpose of the latter two gems, but jruby-launcher is unnecessary for JRuby on Windows or Cygwin because we already ship a native binary there. I think this needs to get kicked back to RVM to remove jruby-launcher and explain the purpose of these other gems (which only appear to install on Cygwin?).
(originally reported at the rvm repo: https://github.com/rvm/rvm/issues/4946)
Environment Information
Provide at least:
jruby -v
) and command line (flags, JRUBY_OPTS, etc)jruby 9.2.9.0 (2.5.7)
uname -a
)Windows 10 (Free VM obtained from here: https://developer.microsoft.com/en-us/windows/downloads/virtual-machines/)
Other relevant info you may wish to add:
Cygwin (latest version downloaded from here: https://www.cygwin.com/)
Expected Behavior
I expect it to install properly like it does on the Mac.
Actual Behavior
Here is a dump of what happened on the command line:
Here is the log file mentioned (/home/User/.rvm/log/1591391509_jruby-9.2.9.0/gemsets.import.global.log):
I am User by the way.
I am not sure if JRuby is supported on Windows 10 + Cygwin + RVM. I didn't read anywhere that it is not, but maybe I'll learn otherwise here.
Thank you.
p.s. I am able to install JRuby just fine using the Windows Installer without RVM. I was wondering if I could use via RVM on Cygwin though for convenience and the advantages RVM offers.