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

JNA version upgrade for Mac M1 chip #201

Closed
mzouink opened this issue Jun 9, 2022 · 8 comments
Closed

JNA version upgrade for Mac M1 chip #201

mzouink opened this issue Jun 9, 2022 · 8 comments

Comments

@mzouink
Copy link

mzouink commented Jun 9, 2022

I am using a Mac M1 and I have a problem with j-blosc and j-hdf5
Exception: (fat file, but missing compatible architecture (have 'i386,x86_64', need 'arm64e'))
Both of them can be solved by installing the c-blosc using homebrew and specifying it in the JVM runtime params
-Djna.library.path=/opt/homebrew/Cellar/c-blosc/1.21.1/lib/
But this only worked with the new version of jna 5.11.0

<jna.version>4.5.2</jna.version>

So it is possible to upgrade jna version to 5.11.0 ?

@ctrueden
Copy link
Member

ctrueden commented Jun 9, 2022

@mzouink I'd love to upgrade this, but it might be a little involved. Not sure until we try.

@mkitti How would this affect your current work on JHDF5 and libblosc?

@mkitti
Copy link
Contributor

mkitti commented Jun 10, 2022

I worked on this with @mzouink earlier.

This is definitely an important intersecting piece of the puzzle. JNA has a native jnidispatch shared library that it needs to function.

For JBlosc support, we need a

  1. jnidispatch native library
  2. Blosc native library

The jnidispatch library only has aarch64 support since version 5 apparently.

@mkitti
Copy link
Contributor

mkitti commented Jun 10, 2022

Is it easier to compile and add a new aarch64 binary to JNA 4 ourselves than to upgrade to JNA 5?

@NicoKiaru
Copy link
Contributor

Related? There's a checklist by @ctrueden regarding some of the changes involved
#163

@mzouink
Copy link
Author

mzouink commented Jun 10, 2022

@mkitti and i will go through the checklist here #163 (comment) today. and we will reach you back

@ctrueden
Copy link
Member

Is it easier to compile and add a new aarch64 binary to JNA 4 ourselves than to upgrade to JNA 5?

I doubt it. And even if so: we should prefer to move forward. It would create more technical maintenance debt, increasing over time, to resist the update.

@ctrueden
Copy link
Member

Shall we close this in favor of #163? I had forgotten about that issue.

@ctrueden
Copy link
Member

Closing in favor of #163.

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

4 participants