Closed tirdadc closed 8 years ago
This is a libv8 issue. Easy way to see:
mdchaney@li212-252:~/hdm-dev.michaelchaney.com$ irb
2.2-head :001 > gem 'libv8'
=> true
2.2-head :002 > require 'libv8'
=> true
2.2-head :003 > Libv8::Paths.object_paths
=> ["/usr/local/rvm/gems/ruby-2.2-head/gems/libv8-3.16.14.7-x86_64-linux/vendor/v8/out/ia32.release/obj.target/tools/gyp/libv8_base.a", "/usr/local/rvm/gems/ruby-2.2-head/gems/libv8-3.16.14.7-x86_64-linux/vendor/v8/out/ia32.release/obj.target/tools/gyp/libv8_snapshot.a"]
Basically, libv8 is saying "my object files are stored in this directory". Still digging on this one, but libv8 is apparently the culprit.
Are you running a 32bit kernel?
The other way around -- rubygems
has difficulties fetching the binary gems for the correct arch whenever one is running a 32-bit userland on a 64-bit kernel.
As a workaround, this worked for me (I needed 0.12.2):
$ gem install therubyracer -v0.12.2 --platform=x86_64
I've recently upgraded to Ruby 2.2.1 on my Ubuntu machine and have been experiencing issues with therubyracer and libv8:
I tried both with and without
--with-system-v8
, uninstalling both libv8 and therubyracer, fixing the versions in the Gemfile, and no luck. Not sure what is going on at this point.These are the lines in my Gemfile:
which result in this in the Gemfile.lock: