error: no matching function for call to 'rb_rescue2' on M1 Mac and v0.6.0
See original GitHub issueI receive the following error when trying to upgrade mini_racer on an M1 Mac running macOS 12 (Monterey). Ruby 2.6.3
mini_racer_extension.cc:1278:14: error: no matching function for call to 'rb_rescue2'
result = rb_rescue2(protected_callback, callback_data_value,
^~~~~~~~~~
Issue Analytics
- State:
- Created 2 years ago
- Reactions:2
- Comments:10
Top Results From Across the Web
Error: no matching function for call C++ - Stack Overflow
I have implemented a B+ tree and it is working fine on Macbook (with CLion) but when I run it on a ubuntu...
Read more >How to install Tensorflow on the Apple M1 Notebook
ERROR : No matching distribution found for tensorflow-macos ... I'd been successfully running M1 native Python code on a MacBook Pro (13-inch, M1, ......
Read more >Error "no matching function for call to" when trying to display
I see a couple of errors. The first is the prototype to the display method is : C++. void Platypus::display(ostream & out) const...
Read more >What to try if you can't install or activate Office for Mac
If you're having trouble installing or activating Office for Mac, you can find self-help troubleshooting steps for common issues.
Read more >Apple M1 Chip: Everything You Need to Know - MacRumors
Apple in November 2020 released the first Macs with an Arm-based M1 chip, debuting 2020 13-inch MacBook Pro, MacBook Air, and Mac mini ......
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Using GitHub Actions, I confirmed that mini_racer 0.6.2 is installed successfully on macos-latest + Ruby 2.6. Thank you for the quick fix!
I just pushed a fix, is it working now when sourced from GitHub?