Jekyll wont appear as a recognized interal or external command

[DonBeleren]

What problems are you experiencing?

Steps to reproduce

What's the output from ridk version?

[DonBeleren]

Ridk version: 2.6.6
It says the following error when installing Jekyll from the the "gem install jekyll bundler" command in the promt.

ERROR: Failed to build gem native extension.

[MSP-Greg]

@DonBeleren

See #96 (comment)

[DonBeleren]

@MSP-Greg
Just went through that, but it still won't let me install Jekyll due to the same error. When I did run the first command from that thread "gem uninstall eventmachine" it did say that "Gem 'eventmachine' is not installed". So I proceeded to run those next two commands.

Please note, I am trying to get Ruby + devkit not just Ruby working. Not sure if this makes a difference..

[MSP-Greg]

@DonBeleren

I don't use (or have installed) Jekyll.

ERROR: Failed to build gem native extension.

Somewhere in the console output it should say what gem failed. Could you post that info? Do you know if you have the 'DevKit/MSYS2' installed? Run ridk exec gcc --version from the console should show output.

[DonBeleren]

Here are two images. The first when the Jekyll command fails. The second looks like an error from running that "ridk exec pacman -Sy openssl" command. I ran the command you gave just now and got version 9.3.0.

Thanks for any feedback you have. I have no clue what to do....

INTERESTING: I went back and looked at the "gem install eventmachine --platform=ruby" command and it gave the same error of " ERROR: Failed to build gem native extension."

[MSP-Greg]

@DonBeleren

I think the following should help:

gem install http_parser.rb --platform=ruby

[larskanis]

@DonBeleren There's a space in the path on your E drive. This leads to failures at gem install.

[MSP-Greg]

Thanks Lars. I always forget about that, even though my RubyGems user-install path (deliberately) has a space...

JFYI, I think it may be specific to some gems, or older Rubies.

[XhmikosR]

Just uninstall any Ruby versions + MSYS2, and start again from scratch. The reason for the second image is that MSYS2 changed some package mirror URLs hence the errors. You could probably just change the URLs, but starting from scratch is the best IMHO.

EDIT: Alternatively, check the instructions by larskanis #184 (comment)