-
Notifications
You must be signed in to change notification settings - Fork 121
libv8 fails to compile with OS X 10.11.4/Xcode 7.3/clang 7.3.0 #205
Comments
+1 I have the same issue. Do you have a solution @RISCfuture ? |
I just compiled libv8 and therubyracer with --use-system-v8 (or whatever the option is called). |
@RISCfuture what version of libv8 did you use in your system to be able to do that? I've tried the one from homebrew master (4.x) and one from homebrew versions (3.15) - didn't work. |
The only way I managed to install it all so far:
|
I tapped homebrew/versions and installed v8-315. |
cool, thanks! |
The following worked for me:
The versions are the ones I needed from my Gemfile.lock. |
Unfortunately the hints above doesn't work for me. I guess it's because of the mismatch of v8 version between 3.15 in brew and the 3.16 that is required by therubyracer. The following worked for me (using older Apple's GCC for compiling):
Change the gem versions according to your Gemfile.lock. Or omit the
|
@joergschiller's bundle config seems to be the best solution. |
Thank you @joergschiller!!! That solved all my issues after trying numerous other avenues, and thanks for including the bundle config! |
Thanks @Haegin your solution worked for me. |
FWIW there's a |
@lloeki That's what I did too. If you only need libv8 for rubyracer (for a rails project for example) It's better to just lock-in the working version (which is just one down), and wait for a patch to libv8 for clang 7.3. |
Nah, if you only need therubyracer for stuff like coffeescript or autoprefixer, you should just install nodejs. Execjs will find and use it and you don't need neither therubyracer nor execjs in your Gemfile. |
+1 I have the same issue |
I fixed the issue with Clang 7.3 in #207. |
Thank. this worked for me |
Should be fixed by #207 |
If you're still having this issue just do a |
See rubyjs/libv8#205 for some details of the problem. It's fixed in 3.16.14.15 of libv8
See rubyjs/libv8#205 for some details of the problem. It's fixed in 3.16.14.15 of libv8
See more information about this issue here: rubyjs/libv8#205
@kovyrin answer worked for me. Kudos |
The text was updated successfully, but these errors were encountered: