Closed Greg-Myers-SB closed 1 year ago
As of now, building gem from source is not supported, although I want to allow it in the future. Right now to use pyroscope we need to use platform specific binaries.
Do you have something like this in your lock file? https://github.com/pyroscope-io/pyroscope/blob/main/examples/ruby/rideshare_rails/Gemfile.lock#L230
If no, try to execute bundle lock --add-platform arm64-darwin-21
This should force downloading a gem with prebuilt arm binaries
Aha! Thanks for the tip on platforms there, this was likely caused by my use of force_ruby_platform
$ bundle config
force_ruby_platform
Set for the current user (/Users/me/.bundle/config): true
Unsetting it fixed my above problem
$ bundle config force_ruby_platform false
$ bundle config
force_ruby_platform
Set for your local app (/Users/me/projects/pyroscope-test/.bundle/config): false
$ bundle
Fetching gem metadata from https://rubygems.org/..
Using ffi 1.15.5
Using bundler 2.3.22
Fetching pyroscope 0.5.1 (arm64-darwin)
Installing pyroscope 0.5.1 (arm64-darwin)
Bundle complete! 1 Gemfile dependency, 3 gems now installed.
Use `bundle info [gemname]` to see where a bundled gem is installed.
If it's unintended for this gem to be compiled then I'm happy for this to be closed. Thanks for the help!
Describe the bug you encountered: This works fine
This causes a large exception
Returns
...
What did you expect to happen instead?
...
How did you install
pyroscope-rs
?pyroscope-rs version and environment
MacOS 13.2 ruby 3.0.4p208 (2022-04-12 revision 3fa771dded) [arm64-darwin21] Bundler version 2.3.22 rustup 1.25.1 (2022-07-12) rustc 1.67.1 (d5a82bbd2 2023-02-07) cargo 1.67.1 (8ecd4f20a 2023-01-10)