-
Notifications
You must be signed in to change notification settings - Fork 192
Conversation
In order to make sure we have valid failures on this branch, and not just a bunch of false negatives, we're only running the C specs, and building with clang. Eventually, we'll merge in support for gcc and more of the test suite. For now, we want to only include the specs we things should be passing
We can decide whether to backport later
I am defeated. @ignisf maybe you can show me where I'm being stupid here. I'm just tring to get it to use either g++-4.8 or a modern version of clang, but I can't seem to have the compile actually use either one of those. |
Will check it out |
I don't believe
after Also there's a clang-compiled ruby version in Travis, I think. |
Ref.
Travis rubies http://rubies.travis-ci.org/ |
Looks like the libv8 binary I'm using is corrupted. It could be that it's using absolute paths for the objects in the archive. I seem to recall us running into this issue before. I can't remember the fix, but it's generating correctly in osx.
|
Ah, right, I remember now. It was generating thin archives on linux, but not mac for some reason. |
|
hallelujah! |
only run C spec compiled with Clang
In order to make sure we have valid failures on this branch, and not
just a bunch of false negatives, we're only running the C specs, and
building with clang. Eventually, we'll merge in support for gcc and more
of the test suite.
For now, we want to only include the specs we things should be passing