-
Notifications
You must be signed in to change notification settings - Fork 121
Binary builds for darwin20 / macOS 11.0 Big Sur #305
Comments
Confirmed this works on my laptop. Thank you! |
This is a gross hack though, and I have encountered a couple of segfaults (still not sure why, just don’t expect this to be 100% stable) but at least it allows the ball to continue rolling. |
How has this not been fixed yet |
will the node based builds work? also ... there is the giant arm question. |
I pushed libv8-node darwin20 builds just yesterday. GitHub Actions secretly has a https://rubygems.org/gems/libv8-node/versions/14.14.0.0.beta2-x86_64-darwin-20 Tested and working against sq_mini_racer 0.3.1. As you can see in the artifacts, it's V8 8.4.371.19. In the future both the gems and intermediate V8 artifact static libs + headers will be available in each run's artifacts: https://github.com/sqreen/ruby-libv8-node/actions/runs/349889868 I'm going to add arm7hf-linux and aarch64-linux at some point, it should be fairly easy with either |
Does this mean that |
@lloeki let me know what gems I should push to rubygems once you have this ready. |
@SamSaffron You would not be able to push the libv8-node gems as is, as they're not a drop-in replacement: I wanted these to be usable in parallel of this libv8 gem, so I namespaced it as But what you can do right away is take the current libv8 8.4.255.0 darwin19 gem and transform it into a darwin20 gem (basically what the above hack does) by replacing all references from one into the other, including the paths and serialised gemspec. This works because Big Sur is binary backwards compatible with Catalina. FYI the segfaults I encountered were -entirely- unrelated to the hack. |
Ok, someone try these 8.4.255.0 (universal is for macOS-provided Ruby, x86_64 is for the others people usually install themselves): https://www.dropbox.com/s/8qt3o6bvx0npst0/libv8-8.4.255.0-universal-darwin-20.gem?dl=0 I did it by skipping the |
Is the libv8-8.4.255.0-universal-darwin-20.gem binary supposed to work both with and without Rosetta? I tried it using mini_racer, and it worked when Terminal runs with Rosetta, but it fails without it. Without Rosetta, it gives this error:
(Tried this on the macOS-provided Ruby.) |
No, it's Intel only, so that's expected. I suppose it could work with Rosetta but I'm unable to test that, lacking the hardware. |
Thanks, it does work via Rosetta. |
I can confirm x86_64 worked for me on Big Sur with rvm |
Gems are now pushed to rubygems! Thanks @lloeki |
Closing this one. I will tracking Apple M1 specific progress over here: #309 |
There is no binary gem published (yet) for 7.3.492.27.1 and 8.4.255.0. I failed to produce one (again because of depot tools acting up).
Not to be outdone, I produced this terrible hack to work around it.
Use as follows:
The text was updated successfully, but these errors were encountered: