0.11.2 fails to build native extensions under 1.9.3-p362 (works under 1.9.3-p327 and 2.0.0-preview2)

[geoffharcourt]

I'm experiencing a compilation error when building native extensions for gem version 0.11.2 in OSX, but they only occur on 1.9.3-p362. Here's the output from the failure:

[~] gem install therubyracer
Building native extensions.  This could take a while...
ERROR:  Error installing therubyracer:
    ERROR: Failed to build gem native extension.

        /usr/local/opt/rbenv/versions/1.9.3-p362/bin/ruby extconf.rb
checking for main() in -lpthread... yes
checking for main() in -lobjc... yes
creating Makefile

make
compiling accessor.cc
compiling array.cc
compiling backref.cc
backref.cc: In member function ‘v8::Handle<v8::Value> rr::Backref::toExternal()’:
backref.cc:35: warning: ‘Wrap’ is deprecated (declared at /usr/local/opt/rbenv/versions/1.9.3-p362/lib/ruby/gems/1.9.1/gems/libv8-3.15.11.1/vendor/v8/include/v8.h:4736)
compiling constants.cc
compiling constraints.cc
compiling context.cc
context.cc: In static member function ‘static VALUE rr::Context::SetData(VALUE, VALUE)’:
context.cc:81: error: no matching function for call to ‘v8::Context::SetData(rr::String)’
/usr/local/opt/rbenv/versions/1.9.3-p362/lib/ruby/gems/1.9.1/gems/libv8-3.15.11.1/vendor/v8/include/v8.h:4826: note: candidates are: void v8::Context::SetData(v8::Handle<v8::Value>)
context.cc: In static member function ‘static VALUE rr::Context::GetData(VALUE)’:
context.cc:85: warning: ‘GetData’ is deprecated (declared at /usr/local/opt/rbenv/versions/1.9.3-p362/lib/ruby/gems/1.9.1/gems/libv8-3.15.11.1/vendor/v8/include/v8.h:4822)
make: *** [context.o] Error 1


Gem files will remain installed in /usr/local/opt/rbenv/versions/1.9.3-p362/lib/ruby/gems/1.9.1/gems/therubyracer-0.11.2 for inspection.
Results logged to /usr/local/opt/rbenv/versions/1.9.3-p362/lib/ruby/gems/1.9.1/gems/therubyracer-0.11.2/ext/v8/gem_make.out

I was able to successfully install v0.11.2 with Ruby 1.9.3-p327 and 2.0.0-preview2. I was able to install 0.11.1 on Ruby 1.9.3-p362.

[ignisf]

This is a duplicate of #231

[cowboyd]

@geoffharcourt my guess is that in only fails in 1.9.3-p362 because that ruby has the 3.15.8.1 gem (which has been yanked). If you remove all stale copies of that gem, then you should be fine.