-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot install on macOS with statically distributed Ruby version #56
Comments
Hello, Thanks for the bug report. I see in your logs:
where those dependencies are coming from? We aren't using them as far as I know. I just tried on macOS Big Sur with Ruby 3.0.0 and it succeeded with no issue.
How did you install Ruby 2.6.6? |
|
Here is a repo with what I need to reproduce on my machine |
Checked the install script (Rakefile), could it be that I don't have |
Tried adding cargo, but doesn't seem to help. Looking closer at the error message, I think this is the failing line: https://github.com/wasmerio/wasmer-ruby/blob/master/Rakefile#L12 Don't know why though, but maybe there are assumptions there, about the host environment, that one shouldn't do in a general install script? Maybe you could check similar install scripts in other gems, and see what they've done? |
Thank you for the investigation. I'll try to find time to address that. I'll keep you updated. |
@Hywan Check out this script from Skylight. They also have a rust-agent, so should be fairly similar to your case. It's also a very well-written gem (one of its authors is a former Rails core team member and (I think) also a former Rust core team member). https://github.com/skylightio/skylight-ruby/blob/master/ext/extconf.rb |
I've failed to reproduce your error even with the given repository. To simplify our debugging session, can you please try to clone this repository, and run: $ rake test I suspect that you have a static version of Ruby, which isn't compatible with how $ ruby -e "pp RbConfig::CONFIG['ENABLE_SHARED']" We should see a |
Yes, you are correct, I have a static version of ruby. I left a comment in rutie (danielpclark/rutie#45 (comment)), about maybe checking if helix has found a solution to this problem. Other than that, I don't have much I can contribute. Still looking forward to trying out wasmer! I'll see if we can change our environment setup to use dynamic ruby. If that isn't easily, we'll have to wait and see if rutie gets support for static builds. Thanks for taking time looking into this! Maybe you could add that check to the rake file, |
Yeah, raising such error is indeed a good idea. For what project would you like to use (Closing the issue as the problem is “solved”). |
Evaluate untrusted code (probably AssemblyScript) in a Rails application. Yeah, feel free to close, agree initial issue is "solved"! Two things that one could do though:
It's up to you and the Wasmer team though to decide, obviously! 😄 Either way I'll keep my eyes on this and hopefully we'll be able to give it a try in 3-6 months, if we're lucky 💯 |
If you're willing to open a PR to raise an error/warning when the Ruby version has been statically distributed, I would be very happy to merge it! I can try to take a look at Rutie itself also, as soon as I've time :-). |
Tried to install on macOS 11.4 (Big Sur) and got this error:
The text was updated successfully, but these errors were encountered: