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
[OSX] dyld: lazy symbol binding failed: Symbol not found: _JVM_FindClassFromCaller #57
Comments
This seems to be the relevant change in the JDK: |
I managed to build a DCEVM targeting a JDK8u25 and it works perfectly! So it would be nice if some new binaries could be released. I suspect this is not an OSX issue so most new JDK8 releases might need new binaries. |
hi Erik, I'm in the same boat and would like to use it with JDK8u30. Could you share what you had to do to make a build? Is it as simple as adding an entry in the gradle.properties for the new jdk (hotspotTag=jdk8u30-b99 for e.g.) and just building it? |
Yeah, that's what I did. I had some problems due to incompatibilites with Clang though. The compiler will complain about unknown flags. Simply go into the Makefile and remove those flags at the relevant places. |
Or build it with GCC, either on your Mac or on another computer, and just lift the compiled binary over. |
ah got it i'll try that. thanks for the information guys |
There is a new fix for new versions >jdk8u20. You shoud uncomment #hotspotTag=jdk8u5-b13 in gradle.properties before build |
great thanks @skybber. this one right? #hotspotTag=jdk8u31-b13 i'll check it out |
#hotspotTag=jdk8u31-b13 Compilation failed with wrong argument format error until I manually commented out /hotspot/src/share/vm/prims/jvmtiRedefineClasses2.cpp:1540. Tests with Oracle JDK 1.8u31 ran successfully. |
8u45 build is available. |
When using JDK8u25 with installer-light-jdk8u5.52 I get the following error:
This might have to do with the version difference, but on OSX Maverick, JDK8u5 is uninstallable due to a bug in the installer, and there's no release of DCEVM for newer builds yet.
The text was updated successfully, but these errors were encountered: