It's a bug in these versions of Ruby.
Example here
Reported here.
Fixed here.
You have to upgrade to a newer version of Ruby (right now that means compile source yourself). It's a bug hit by the suite, not the lib, so shouldn't matter to end-users. This is how I built mine:
Didn't have a ./configure, so I Had to install autoconf
$ brew install autoconf
Then generate the ./configure
$ autoconf
Then run configure to get a Makefile. This prefix is for chruby, you'll do something different if your rubies get installed elsewhere.
Then make install to put the compiled files where they belong
$ make install
Now you can use it (you may have to launch a new shell). I may have also had to make the "$HOME/.rubies/ruby-2.2.0" dir myself, not sure b/c I got confused and did that when the problem was something else.
It's a bug in these versions of Ruby. Example here Reported here. Fixed here.
You have to upgrade to a newer version of Ruby (right now that means compile source yourself). It's a bug hit by the suite, not the lib, so shouldn't matter to end-users. This is how I built mine:
Didn't have a ./configure, so I Had to install autoconf
Then generate the ./configure
Then run configure to get a Makefile. This prefix is for chruby, you'll do something different if your rubies get installed elsewhere.
Then make to compile it
Then make install to put the compiled files where they belong
Now you can use it (you may have to launch a new shell). I may have also had to make the "$HOME/.rubies/ruby-2.2.0" dir myself, not sure b/c I got confused and did that when the problem was something else.