Closed anilreddy closed 8 years ago
@anilreddy please read the Rubyinstaler announcement notes:
https://groups.google.com/d/topic/rubyinstaller/AnVOc_cosTw/discussion
Existing pre-compiled gems might not be Ruby 2.1 compatible
Ruby 2.1 introduces ABI breakage which means compiled C extensions with previous 1.9.3 or 2.0.0 will not run against Ruby 2.1.
DO NOT install Ruby 2.1 on top of existing Ruby 1.9.3 or 2.0.0, or try to use compiled extensions with it.
You will be required to force compilation of those gems:
gem install <name> --platform=ruby
This will require you have the extra dependencies installed for that gem to compile. Look at the gem documentation for the requirements.
Please check each gem documentation and recent releases.
That means you need to do: gem install gherkin --platform=ruby
to trigger compilation.
It will take time for gems to bundle binaries for Ruby 2.1, so please be patient.
Gherkin 3 (work in progress) will be pure ruby, so these problems should go away when that happens. It will take several months before we're there though.
Hi Aslak,
Could you please tell us what version of cucumber/gherkin/ruby is compatible with each other, if we have 64 bit Windows 7? It is VERY hard to find the components that work together. Just an example would be great!
+1 for @melikeercan's comment... Cucumber has been pretty much unusable for us as a windows only shop because of this issue.
@melikeercan > After several hours wasted, and tons of tries.. I finally got cucumber to run on my system.
https://github.com/cucumber/gherkin/issues/273
@mscharley has a comment in the above thread that doing gem install gherkin --platform ruby would work on windows in combination with changing the prefix = '' in the c_lexer.rb file. This did not work for me AT FIRST...
I had to uninstall all of the previous gherkin gems which all threw an error about ill formatted specs. So I deleted all references/specs/gems/folders to gherkin and redid @mscharley's suggestion. Worked perfectly!
I got this idea from @jnyman in that same thread where the original version(s) of gherkin were compiled with mingw32. Hope this helps!
Hi @nhudacin
Could you please explain or show how can you solve the issue or if anyone can help me on this repo. I could not run any android test on my machine because of this gherkin issue. I delete the gherkin 2.12.2 from gem folder and trying to install again with "gem install gherkin" but it always gives me error : Error installing gherkin: failed to build gem native extension etc. It also put the folder on the same location but when I run my test with "calabash-android run
@alpersilistre - For me, I had to remove the installed gherkin (it was named something like gherkin-2.12.1-x86-ming32). The ming32 x86 is what was causing the issue in my case. I needed the x64 compiled version.
gem uninstall gherkin --force
I have ChefDK installed which comes pre configured with the ruby dev kit needed. It sounds like you may not have the ruby dev kit or if you do, it's not configured correctly and probably isn't an issue with Gherkin. You will eventually need to install and compile the gherkin gem on the machine you're trying to run it on...
gem install gherkin --platform ruby
The "--platform ruby" is important here. If you don't use this switch then you'll just download the x86 gem again.
The uninstall / install worked for me Ruby 2.1.6
Please try Cucumber-Ruby 2.1 which uses the new Gherkin3 parser.
Hi,
Today I have upgraded ruby ver. to 2.1.3 in windows 8 OS and executed a selenium script with cucumber and I came up with this issue. Let me know if you need more info.