Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Add support for Ruby 2.0 #116
You can use that to install yajl-ruby without issues:
@luislavena thanks for the information. To be honest, i did know that trick.
However, the problem is that i'm not aware of the possibility to specify that
This means that Bundler will install and load always the precompiled version of the
The problem appears like this:
As you can see then Bundler detected that there is a precompiled
Please let me know if there's a workaround for such a situation.
If there's not, then please reopen this issue and:
I know it's kindof a pain in comparison, but you should be able to download the .gem file itself (not the pre-compiled one) and stick that in your bundle's cache directory and have it use that instead. I haven't verified that on Windows, but that's how it works everywhere else I know of.
I'll reopen this until I get a chance to push out another cross-compiled build with 1.8, 1.9 and 2.0 versions inside. What a pain...
Bundler used to detect already installed gem and use that skipping
Perhaps you have isolation enabled?
Sorry for top posting. Sent from mobile.
There is a setting in bundler config that disables usage of system wide
I used to manually install the gem (with compilation) and then simply do
What is the output of "bundle config" inside the directory of your gemfile?
Sorry for top posting. Sent from mobile.
$ Gem install yajl-ruby
facing below error when i ran this command : jekyll build --source "templates" --destination "dev"
c :/ Local/Ruby/ruby-2.0.0-p0-i386-mingw32/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb: 45: in
If you see lower in the backtrace:
You have x86-mingw32 gem installed.
As mentioned in the RubyInstaller release notes:
Bundler will keep attempting to install x86-mingw32, so you will need to be careful when doing
One more piece of the puzzle. It turns out bundler, prior to version 1.4, doesn't recognize 64 bit gems on Windows bundler/bundler#2658 which causes the problems noted above.
A full workaround appears to be:
A full article can be found here.
This was referenced
Jun 28, 2014
I was able to use gem-compiler to get a binary gem for v1.2.1 for Ruby 2.0 on Windows that works built using gem-compiler.
The gem can be downloaded here (depending on the level of trust you have in me):
Or you can build it yourself by installing rubyinstaller, the devkit and running
To use the binary gem:
However, what led me to this problem in the first place (foodcritic from Chef - see [https://github.com/opscode/chef-dk/issues/124](this issue)) still has a problem because it's gemspec puts a restriction of '~> 1.1.0'.
That was the only safe way to cover Windows and Unix on Ruby 1.9, but in order to change it to '~> 1.2.1', rubygems.org has to host a binary version of the 1.2.1 gem. Otherwise your app will work on Unix and fail on Windows.
So what is really needed here is for Brian or Lloyd to upload a Windows binary gem for v1.2.1 to rubygems, which will let people who consume yajl-ruby up their spec version to v1.2.1 and everyone should be happy.
Unsure who is maintainer of this gem, but: you can use rake-compiler-dev-box to cross-compile yajl-ruby within OSX/Linux to Windows:
All instructions on usage there. You can also include support for 2.1.x since is enabled by default.
Hope this helps.
@luislavena: well, we have this given situation. yajl-ruby breaks pygments.rb which in turn breaks Jekyll on Windows with Ruby >= 2.0. This is my problem I'm trying to find a solution once and for all.
I don't have a lot of experience with Ruby, but we really need to get this fixed. Not for me, but for everyone's sake. Otherwise we will be stuck with Ruby 1.9.3 for a lot more. Which wouldn't be so much trouble but the next Jekyll version will drop 1.9.3 support.
I hope you see my point of view here. :/
@XhmikosR pygments is no longer mandatory for Jekyll, you can use Rouge instead.
Since you're not familiar with Ruby, crash course:
That is the process, so I leave to the gem maintainer to decide what or how to do it.
I feel your pain that this is a problem, needs to be solved, etc, etc. But fixes to projects cannot happen magically or by continuous me too reports on issues. Fixes happens when people contribute or provide help or assistance.
Either Jekyll maintainers or contributors should step up and take the issue on their side, since they are the ones going to drop support on 1.9.3, not me, neither yajl-ruby developers.
You, me or zillion more folks being annoyed by this will not get this fixed.
Hope you see my point of view.
@luislavena: I'm completely aware of the rouge alternative. I don't manage GitHub pages though, and they use pygments.
Also, give me a break, I didn't know I wasn't allowed to express myself when something like this big affects me.
There's clearly an issue, and it needs to be fixed. Backwards or not, from whoever responsible.
Sure, take a break, relax, have fun.
Sure gem maintainers or contributors will carve some of their free time (you know, that one that happens between paid work and family and friends) to come and work on projects just to fix problems of others that do not care at all about their effort put free on projects, simply because you think you deserve or entitled to get a fix, because you know, all the money you have put on this project.
As you express yourself, sure I believe I'm allowed to express myself
yajl-ruby uses rake-compiler:
To compile things.
Was created by me 6 years ago precisely to provide binaries for Windows users so they shouldn't be suffering by installation problems (aka: you)
Last year, to make things more simpler, another developer, from frustration wanting to release bcrypt gem for Windows users created rake-compiler-dev-box:
Which is another tool for gem authors to make it more easy to release gems for Windows users so they don't suffer (aka: you don't suffer).
So sure, vent out all your frustration since open-source developers are also your therapists that need to listen to your complains while also fix your problems.
The solution was provided, but perhaps gem author is busy or have other things to attend, have you considered that?
Instead of saying how affected by this you and others are, perhaps any of the Jekyll developers can step up and offer help instead of complaining?
I believe there are other Ruby developers that contribute to Jekyll that care enough for Windows users that can help out? (At least the documentation of Jekyll says that: http://jekyllrb.com/docs/windows/#installation)
You see, the attitude you present goes along the lines of other users who believe that because someone's creation was shared and made freely available for others to benefit is enough reason for them to become your support line, therapist and repairman.
You stated that you didn't know (or care) on how Ruby and gems work (or were released). The comment I gave previously aimed to provide guidance to the gem author and/or maintainer to ease them the process to release those gems.
My comment wasn't directed at you, or to you, but you decided that the information I provided didn't solve your problem and that was good enough to keep complaining about it.
If you think I trolled you by my statements, please accept my apologies.
But if after reading all this you still believe gem author or maintainer owes you something, please go see an specialist, or give that money to any developer that is willing to help out solve this, but do something that doesn't involve complaining.