-
Notifications
You must be signed in to change notification settings - Fork 190
Does not build on OSX mavericks with ruby 1.9.3-p194 #277
Comments
+1 |
@mpapis can you elaborate? For the most part, we're just deferring to https://github.com/cowboyd/therubyracer/blob/master/ext/v8/extconf.rb |
That said, on my fresh mavericks install:
|
@cowboyd this happens on older patchlevels then p448, they were not possible to build with anyway ruby 1.9.3 any patchlevel even if you were able to compile it with @banister can you run this one: rvm config-get --all | grep -E 'CPP|CXX|CC|gcc|clang' |
|
it looks like the problem could be https://github.com/cowboyd/therubyracer/blob/master/ext/v8/extconf.rb#L10 |
same on
|
I got it fixed by a dumb solution:
Aparently the problem is in libv8 (3.3.10.4) gem that is not building on a mavericks system, for that reason the "libv8.a" is never created. |
@mpapis hmmm... That line should never get used on OSX systems since it does an explicit check for |
I do not have right now access to an OSX system, would need to see resulting |
I tried a few of the above solutions, but still no fix. Any progress on a more permanent patch? Edit: At work we've remove this gem from our current workflow temporarily since multiple people seem to be having the same issue. |
@ashblue have you tried the "fix" i have proposed? |
Yes, "bundle install" would run correctly. But "rails s" would crash saying that therubyracer was not installed. |
Newer versions of libv8 build on mavericks. Is it possible to update libv8? |
@michaelharro, could you me more specific? Which versions exactly? |
@ignisf sure. We have a project that uses libv8. We were using gem 'libv8', '=3.11.8.17' and couldn't build on mavericks. I saw this http://stackoverflow.com/a/19586282 so I did some trial and error. I couldn't get any of the 3.11 versions to build on mavericks but all the 3.16 versions I tried worked just fine. So somewhere between 3.11.8.17 and 3.16 it was fixed. |
I was the having the same issue with 0.10.1 and 0.10.2 on OSX Mavericks. @alecslupu's fix worked for me, but rails s, as well as rake db:create and several other commands would fail with |
@valachi I am running Rails 3.2.12 And i don't have any issues ... and therubyracer (0.10.2) |
@valachi, yes, there are a bunch of fixes in the 3.16 tree. I have released a binary version for Mavericks of libv8 3.11.8.17 so you should be able to use it without the need to compile. We will probably release a new version in the 3.11 branch once the new changes in the 3.16 branch prove to be stable. |
I'm also seeing a segfault when trying to require rubyracer/libv8 on mavericks. Managed to install them fine. |
I tried the symlink solution, as well as upgrading to newer versions of both |
@mjjohnson did you try the latest version in the libv8 master branch? The patches necessary for compilation with clang and GCC 4.2 are in and need to be tested before we release. |
@ignisf I hadn't tried that yet. :) I'm just getting an existing project running on my local box, and so for me it's better to be able to use the version they already had. But I can temporarily try from the master branch if you like. |
The solution shared by @mjjohnson worked perfect for me too. Thanks. |
+1 |
The solution suggested by @mjjohnson worked for me as well. |
Nice work @mjjohnson 👍 |
I talked to @mpapis (from #rvm channel on freenode) and he stated it was due to therubyracer not using the
CC
variable from Ruby:The text was updated successfully, but these errors were encountered: