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

Update openjfx to fix Apple M1 compatibility #373

Open
vbabenkoru opened this issue Jul 15, 2021 · 1 comment
Open

Update openjfx to fix Apple M1 compatibility #373

vbabenkoru opened this issue Jul 15, 2021 · 1 comment

Comments

@vbabenkoru
Copy link

vbabenkoru commented Jul 15, 2021

Describe the bug
When launching okta-aws on a Mac with Apple M1 processor (aarch64), it crashes with the following message:

Loading library prism_es2 from resource failed: java.lang.UnsatisfiedLinkError: /Users/victor.babenko/.openjfx/cache/12.0.1/libprism_es2.dylib: dlopen(/Users/victor.babenko/.openjfx/cache/12.0.1/libprism_es2.dylib, 1): no suitable image found.  Did find:
	/Users/victor.babenko/.openjfx/cache/12.0.1/libprism_es2.dylib: mach-o, but wrong architecture
	/Users/victor.babenko/.openjfx/cache/12.0.1/libprism_es2.dylib: mach-o, but wrong architecture
java.lang.UnsatisfiedLinkError: /Users/victor.babenko/.openjfx/cache/12.0.1/libprism_es2.dylib: dlopen(/Users/victor.babenko/.openjfx/cache/12.0.1/libprism_es2.dylib, 1): no suitable image found.  Did find:
	/Users/victor.babenko/.openjfx/cache/12.0.1/libprism_es2.dylib: mach-o, but wrong architecture
	/Users/victor.babenko/.openjfx/cache/12.0.1/libprism_es2.dylib: mach-o, but wrong architecture

To Reproduce
Steps to reproduce the behavior:

  1. Install okta-aws-cli-assume-role on a Mac with Apple M1 CPU
  2. Run okta-aws in command line
  3. See error

Expected behavior
It should run normally.

Additional context
This was fixed in openjfx 16+6 and higher: openjdk/jfx@e1adfa9
Updating to 16 doesn't help, and 17 isn't on maven yet. Specifying latest version of 17+* helps though.

@giladsh1
Copy link
Contributor

giladsh1 commented Mar 14, 2022

A a workaround you can use a build of the Zulu-JDK with FX support.
Make sure to use JDK FX version 11, since it's the only one that works

https://www.azul.com/downloads/?version=java-11-lts&os=macos&architecture=arm-64-bit&package=jdk-fx

Verified on macOS with M1 Pro.

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

2 participants