-
Notifications
You must be signed in to change notification settings - Fork 93
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
dyld: Symbol not found: __ZN2v82V813InitializeICUEPKc #185
Comments
Could this be a duplicate of #169? |
This is on Mac OSX so it doesn't seem to be the case. |
I am getting the same error on Mac OSX with an M1 chip (arm64). I also tried ruby 2.7.0 and 2.6.6 und tried installing mini_racer and libv8 as x86_64 with |
I had this issue as well with my Rails 6.1.1 Install on Apple Silicon. here's the relevant thread: and the beta build for your Gem file:
|
Is the issue still resolved for you, @sweetppro using the latest released version of |
yup I'm running mini_racer (0.4.0) without any issues |
There have been a ton of updates/fixes with current mini_racer versions. Can you check if the current 0.6.2 solves your issue, @Overload119? |
No longer can reproduce. |
@tisba I found this thread because I've been fighting this same issue for 2 days on version 0.6.2 using an Intel Macbook Pro OSX Big Sur and more recently Monterey. The error I was getting on Monterey when attempting to start a rails server was
Because @sweetppro said 0.4.0 worked for him I figured I would give that a shot
I'm finally able to run my rails app again using mini_racer 0.4.0 where I could not on 0.6.2. |
@scruff311 that's really odd. I'm on Monetery 12.1 (intel/x86), also using RVM like you and with Ruby 2.7.5, mini_racer 0.6.2 and libv8-node 16.10.0.0 it just works. Can you tell us some more about your environment?
The only thing I can think of at this time is to re-install mini_racer and libv8-node. If that doesn't help I'm lost /cc @SamSaffron |
@tisba here is the output i get for those commands
|
It's a stretch, but could you remove all versions of |
I noticed something else: Your |
🤯 i uninstalled To answer your question, my Ruby 2.7.5 was installed with RVM when my mac was still on Big Sur (darwin-20). I have since updated to Monterey (darwin-21). Thanks for your help! |
Awesome! 🎉 I'm collecting these kinds of issues currently to compile a troubleshooting guide. This platform difference is an important piece of it! |
Thank you for documenting these steps, @scruff311. I tried what you did (I was only uninstalling mini_racer) and was able to get my local working again. |
@tisba When I run my local Rails server, I encounter this:
I previously encountered this error while upgrading to Ruby 3.0.0 last month. I've just upgraded to Ruby 3.1.1. I was able to clear up this issue last time by uninstalling mini_racer and libv8-node at the same time. However, it didn't work this time around. Any tips? My specs:
|
@cjoulain are you 100% certain that you've compiled Ruby, |
Thanks for checking in, @tisba. I had to uninstall and reinstall almost 10 times for my repo to work again. I can't say what helped -- it working again was arbitrary. But I did compile all three. Since you mention it's OS-related, I won't reach out here if it happens again. |
I'm running out of ideas then :( Is there some way to further analyse what's going on here, @SamSaffron/@lloeki? |
In my case, I resolved the issue by updating my clang++, clang, c++, gcc, and g++ on macOS to Apple Clang. Here's the setup for g++, gcc, and c++ in .bashrc or .zshrc files. Please ensure these lines are placed at the beginning of file:
After making these changes, check the versions of the following:
Ensure that the versions match Apple Clang, as this error is likely caused by our compilation. Finally, restart machine, reinstall mini_racer, and it should work fine. |
This occurs when server-rendering from React component.
The gem install command actually works fine.
Any idea what I can do here to debug?
The text was updated successfully, but these errors were encountered: