I was face the same problem on ubuntu:
After some experimentation I was able to confirm that 'gem install therubyracer --pre
' on the command line worked okay, but telling bundler to use the --pre
option didn't work:
bundle config build.therubyracer --pre
I don't know if that was because the gem was being pulled in via a dependency and not by an explicit 'gem' line in the Gemfile. I was unable to fix this even after extensive Googling, but since 0.11 seems to be only a few hours old I decided to try reverting to the previous 0.10
version by adding:
gem 'therubyracer', '=0.10'
before the use of the gem that depended on it. This forced bundler to pick the earlier version and it installed like a charm. Hopefully someone will fix 0.11
soon enough.
After looking at the issues for therubyracer on github this seems to be related to two different issues - one closed: https://github.com/cowboyd/therubyracer/issues/213 which suggests installing the libv8 gem first (or explicitly), and that causes a different error: https://github.com/cowboyd/therubyracer/issues/215 and that is not yet closed - the libv8 gem seems to have a corrupted binary in it for 64-bit targets. The only solution appears to be to build libv8 from source or do like I did and back up to 0.11beta8 or earlier (someone says 0.11beta8
works). Until then I suggest you watch the 215 issue on Github and await a fix.
Thanks.