This repository has been archived by the owner on Dec 4, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 121
libv8 3.16.14.9 breaks build on travis #174
Comments
👍
Happens on ruby Gem version |
I've yanked this version of the gem until I can find out what's going on. |
@atz I still cannot understand why rubygems is not matching yosemite to the binary gem 😠 You should not be having to ever compile libv8 for yourself. |
@cowboyd take a look at rubyjs/therubyracer#316 (comment) |
Thanks a lot. @ignisf I didn't found the *.h-file you mentioned in the travis output. Maybe you've got a different problem than me? |
@cowboyd dunno, RubyGems version was |
fwiw, I've opened this rubygems/rubygems#1299 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi,
using
libv8 3.16.14.9
on travis breaks a build. Usinglibv8 3.16.14.7
does not break the build. I'm not sure if it's the fault oflibv8
, but at least it seems to be a fix to use an older version of the library. TheGemfile
can be found here. TheGemfile.lock
is only available on travis. It is not part of the build. Any other information you need to help me?The the log can be found here. It segfaults:
The text was updated successfully, but these errors were encountered: