-
Notifications
You must be signed in to change notification settings - Fork 285
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
missing symbol called #568
Comments
I'm able to reproduce this issue when I use arch -x86_64 zsh
nvm use 18
node main.js ---> If I build the native module in ARM, and use Node.js ARM ( I also tried to build the native module on a real x64 macOS virtual machine, then force use it by patch-packaging the bridge, without success. Just for context, I'm using |
Update : Thanks to https://groups.google.com/g/node-java/c/Yj4F7Zrbb0k, I succeed to use Java when process.env.DYLD_INSERT_LIBRARIES = path.join(jrePath, 'lib', 'server', 'libjvm.dylib') |
I've managed to get things working under Rosetta, which can be documented for the next person running into it. As mentioned, you can fully move everything into the arm64 space, however you can also move everything into the x64 space and execute under Rosetta. However, this requires downloading a JVM which is an x64 build manually and setting your JAVA_HOME to the absolute path of that installation. I did this with: node v20.12.0 (still issues building with node v22 unfortunately due to the node API mismatch #580) And I did patch the compile-java.sh so that I could use a newer java version: #javah -classpath src-java -d ./src node.NodeDynamicProxyClass All tests pass. |
When I try to do something like this (i.e. basic stuff)…
…I get an error like this:
environment
Any idea what’s going wrong?
The text was updated successfully, but these errors were encountered: