-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Native gem installation doesn't work on Windows with >= 2.4.0 #977
Comments
I'm seeing this as well with Rubygems 2.4.1, ruby 1.9.3p545 (2014-02-24) [i386-mingw32]. |
It looks like @b97ec2a will only work on Ruby 2.0.0 and newer so I will update it to not apply to early ruby. |
Got the same error, in Rubygems 2.4.1, ruby 1.9.3p545 (2014-02-24) [i386-mingw32]. C:/Ruby193/bin/ruby.exe -r ./siteconf20140728-2956-j82opf.rb extconf.rb make clean make make failed, exit code 2 Gem files will remain installed in C:/Ruby193/lib/ruby/gems/1.9.1/gems/json-1.8. C:\Ruby193>ruby -v C:\Ruby193>gem --version |
Same issue as above.
|
@hehahovip @petedunc88 there is a issue with newer RubyGems and Ruby 1.9.3. Until that is fixed, please revert to older version of RubyGems. |
I am having the same exact error, except with executing gem install debugger RubyGems 2.4.1 & Ruby 1.9.3-p429 w/ DevKit installed. |
Is there any progress on this? I am getting the same error. |
No. I eventually switched over to Ubuntu Linux OS and my issue has been resolved
|
@ishristov as commented before and also on RubyInstaller mailing list, if you're using Ruby 1.9.3, please downgrade to 1.8.29: https://groups.google.com/d/topic/rubyinstaller/k19SeJijpKU/discussion |
I guess |
I confirm that gem update --system 2.3.0 is working (windows 8.1 x64) but 2.4.0 and 2.4.1 fails |
gem update --system 2.3.0 |
Not corrected in 2.4.2 |
Yeah. I still have to use the solution I mention a few posts above.
|
Nope, its still open, I haven't had time to fix it yet. |
gem update --system 2.3.0 worked for me too. Had to downgrade it from 2.4.1. |
Downgrading to gem 2.3.0 worked. Thanks a lot! |
I was working on APPIUM and thanks Downgrading to gem 2.3.0 worked. Thanks a lot! |
Thanks folks, downgrading worked for me too. |
Thanks a lot!! I have been searching for this solution for long time, was not able to use debugger with rubymine. Downgrading to gem 2.3.0 worked. |
Worked for me! Thanks! Spent the last 2 days trying to get this to work !@#! |
thanks. It helped in installing mongoid for me. |
I'm still getting this issue in 2.4.5 - reverting to 2.3.0 fixed it thankfully. Almost lost it.. also, I did get this https issue which lead me to running gem --update-system |
@duckinator awesome, thanks for figuring this out! It seems like applying your suggested change would result in 1.9.3 acting the same way as it did before commit b97ec2a, and 2.0.0 acting the same way as it does after b97ec2a. I'm satisfied with that solution, since nothing is worse than it was before. Let's make that change and release a new 2.5.x version with the fix. That way everyone can simply run Everyone who has participated in this ticket, please consider upgrading to a newer version of Ruby. Ruby 1.9 no longer gets patches of any kind, even security updates, and Ruby 2.0 will only get security fixes until Feb. 24, 2016, when Ruby 2.1 will be moved to security-only fixes. If you want (or need) actual bugfixes in Ruby, please upgrade to Ruby 2.2 or 2.3. |
Pull request #1453 should resolve this, with the caveat that if you are using Ruby 1.9 on Windows and |
Same issue. Switched to Kali Linux and it fixed my problem |
@duckinator OSX also suffers from this... :/ |
What does |
@duckinator I was using the latest. 2.6.x. I also tried to revert to using gem update --system 2.3.0 but with the same result. :/ it's not a big deal actually, because the project I'm working on just declared 1.9.x EOL. :) Which, I think is a very good move. |
C:\Windows\system32>gem update --system 2.3.0 please help me im using windows 8.1 |
Could not install rainbow 2.2.1 on Windows 7. Tried to fix it using DevKit. https://github.com/oneclick/rubyinstaller/wiki/Development-Kit#building-the-devkit After following the instructions, still not worked. Native gem installation doesn't work on Windows issue. rubygems/rubygems#977 And finally make it work.
Hi, I am still experiencing this same issue on an fresh install of Any suggestions? |
This issue started with Ruby 1.9.3. Please post more info. I am familiar with newer Ruby versions on Windows... |
@MSP-Greg I am trying to install Jekyll. I already installed I have tryed to downgrade to Ruby Info
Installing JekyllI run:
I get:
|
The issue is building the gem |
|
I haven't looked at the
It looks like your MSYS2/MinGW install is incomplete. Maybe something like:
|
You are right. I will have to configure pacman to trust a custom certificate to allow it to connect and download the packages. I get the following message when I run the command that you suggested.
Will you have an idea of how to do that? I had to do the same for npm, Vagrant, Ruby, git, wget... Each software has it's own peculiar way to get them configured, e.g. wget: https://stackoverflow.com/questions/22282013/how-to-use-wget-with-ssl-certificate/50494174#50494174 |
I work quite a bit with OpenSSL (I'm trying to build Ruby trunk with openssl/openssl master right now, works locally but not on Appveyor...) I've never had an issue with Ruby or pacman. Any idea where the 'self signed cert' is? What does Otherwise, I'm not sure, but this isn't a RubyGems issue... |
The self signed certificate recides at the corporate's proxy server 🙄. On windows the environment variable I will try to look into. So, I think you are right. It is not a ruby issue at this point. Thanks so much. I did had to configure ruby to use the self signed certificate. I got the public certificate, I put it on the folder Now I have to iron out the |
I appear to get the same issue on Windows:
|
See https://github.com/tenderlove/av_capture That gem is MacOS/OSX specific. |
Wow! I... feel ridiculous. :P |
Trying to install a native gem on Windows doesn't work with RubyGems >= 2.4.0, Ruby 1.9.3-p547. DevKit is installed. As far as I can tell, this is related to b97ec2a
If you look at the Makefile, you see:
With rubygems < 2.4, the Makefile would look like:
The text was updated successfully, but these errors were encountered: