-
Notifications
You must be signed in to change notification settings - Fork 123
Installing on ubuntu 12.04 fails? #47
Comments
Hi, I was able to compile locally, not sure how to proceed to include the binary or where to find the binary at all (see also #48). |
We're having a similiar issue on centos 6.3. I was able to build the binary gem manually, but:
As you can see, it still knows about the I didn't figure out how to make a completely self-contained binary build, so I'm now always compiling the thing on installation... |
Ok, I was able to do a
And then building therubyracer gives me the following errors:
Any ideas? |
@averell23 I can see the same as you, but I am not entirely sure if that explains the error I am receiving. Frankly, while I have done loads of C/C++ development ages ago, I can't read or interpret the |
It looks as though it is finding and using an old version of v8 which did not take a parameter to IdleNotification() /usr/include/v8.h should not be used. Instead it should find the version of v8.h contained in the libv8 gem. |
Note that this may very well be a bug in libv8 itself |
Ok. I had two weeks holiday, and now my bundle installs perfectly fine. Not sure if that means therubyracer was fixed, or libv8 or something in ubuntu. Anyway: this issue is no longer relevant for me. |
I have the following in my
Gemfile
:I get the following error when compiling:
I can see the last commit should fix a corrupt binary for x64, so when I try the following in my
Gemfile
I get the following error:
Any ideas??
The text was updated successfully, but these errors were encountered: