Skip to content
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

Cannot load GKL with java 11 on OSX Mojave #102

Closed
lbergelson opened this issue Sep 18, 2019 · 1 comment
Closed

Cannot load GKL with java 11 on OSX Mojave #102

lbergelson opened this issue Sep 18, 2019 · 1 comment

Comments

@lbergelson
Copy link
Contributor

I'm unable to load the GKL dylibs when running under Java 11. I'm not sure if this is specific to OSX or if it is true for linux too. I get the following error:

1:51:12.613 INFO  NativeLibraryLoader - Loading libgkl_compression.dylib from jar:file:/Users/louisb/Workspace/picard/build/install/picard/lib/gkl-0.8.5.jar!/com/intel/gkl/native/libgkl_compression.dylib
11:51:12.628 WARN  NativeLibraryLoader - Unable to load libgkl_compression.dylib from native/libgkl_compression.dylib (/private/var/folders/q3/hw5cxmn52wq347lg7rb_mzlw0000gq/T/louisb/libgkl_compression1725451455108434181.dylib: dlopen(/private/var/folders/q3/hw5cxmn52wq347lg7rb_mzlw0000gq/T/louisb/libgkl_compression1725451455108434181.dylib, 1): no suitable image found.  Did find:
	/private/var/folders/q3/hw5cxmn52wq347lg7rb_mzlw0000gq/T/louisb/libgkl_compression1725451455108434181.dylib: code signature in (/private/var/folders/q3/hw5cxmn52wq347lg7rb_mzlw0000gq/T/louisb/libgkl_compression1725451455108434181.dylib) not valid for use in process using Library Validation: mapped file has no cdhash, completely unsigned? Code has to be at least ad-hoc signed.)

It seems like this is a new "feature" from apple to prevent you from running any code that hasn't be submitted to apple for notarization, but it only seems to apply when running java 11 at the moment and not to java 8.

@lbergelson
Copy link
Contributor Author

Huh, this seems to be an openjdk bug that's being actively worked on and should be resolved for mojave adoptium/temurin-build#1211.

It was triggered by enabling some sort of additional osx security feature, which is optional now but is going to be mandatory in the next version of osx. So this will probably re-ocurr in osx 10.15.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant