Open jmspring opened 3 years ago
I think I am running into the same error. If it's of any use:
% sw_vers
ProductName: macOS
ProductVersion: 11.4
BuildVersion: 20F71
@jmspring @mikera I've added M1 support with PR https://github.com/terl/lazysodium-java/pull/107. It is also merged into the master branch. But we have to wait for the next release.
Could you checkout the master branch, compile the project (e.g. gradle install
), and check if this works for you?
@gurpreet- Could you release a new version, so Lazysodium will officially support M1?
+1 for this. Would appreciate it as we have come across this issue using the library on an M1 mac.
Release 5.1.0 contains the new M1 enabled binary. Bonus: Libsodium has been upgraded to 1.0.18
too.
If any of you has an M1 mac could you please test this 5.1.0?
Just upgraded to 5.1.0
and it seems to break on Windows, relevant error:
java.lang.UnsatisfiedLinkError: Unable to load library 'C:\Users\Mike\AppData\Local\Temp\resource-loader1351855501828376432\windows64\libsodium.dll':
The specified module could not be found.
The specified module could not be found.
Native library (win32-x86-64/C:\Users\Mike\AppData\Local\Temp\resource-loader1351855501828376432\windows64\libsodium.dll) not found in resource path ......
I can test on M1 later today if I can get the Windows version working!
Just upgraded to 5.1.0 and it seems to break on Windows, relevant error
I can confirm, that https://github.com/terl/lazysodium-java/commit/e0c49d6fa7eaecb01218eb8ce013ef20562ad9e3 breaks the windows version.
Tested e0c49d6 on the following systems:
OS | Arch | Operational |
---|---|---|
MacOS | Intel | :heavy_check_mark: |
MacOS | ARM | :heavy_check_mark: |
Ubuntu | Intel | :heavy_check_mark: |
Raspbian | ARM | :heavy_check_mark: |
Win x64 | Intel | :x: |
Edit: I compiled the latest https://github.com/jedisct1/libsodium/tree/stable branch of libsodium on Windows 10 x64 myself. The dll unfortunately does not run under Lazysodium either. Is it possible that a new API or similar has been added?
@gurpreet- Maybe https://github.com/terl/lazysodium-java/pull/111 does fix the problem.
Hey @KevinRoebert, Libsodium does indeed publish its stable Windows binaries directly here https://download.libsodium.org/libsodium/releases/.
I have downloaded the binaries again and committed them into Lazysodium. Are you able to test either the latest master branch? Or you can test via the snapshot 5.1.1
?
Hey @KevinRoebert, Libsodium does indeed publish its stable Windows binaries directly here https://download.libsodium.org/libsodium/releases/.
I have downloaded the binaries again and committed them into Lazysodium. Are you able to test either the latest master branch? Or you can test via the snapshot
5.1.1
?
The master branch does work under Windows 10 x64. But I would still suggest that the same library versions should be used for the tests and the actual wrapper. Otherwise, the tests will run, but the production code will not.
For this purpose, I have created the MR https://github.com/terl/lazysodium-java/pull/112.
Thank you for the PR @KevinRoebert. I've merged it 😄
I've just released version 5.1.1. Everything should work in there.
Thank you for the PR @KevinRoebert. I've merged it 😄
I've just released version 5.1.1. Everything should work in there.
Tested on the following systems:
OS | Arch | Operational |
---|---|---|
MacOS | Intel | :heavy_check_mark: |
MacOS | ARM | :heavy_check_mark: |
Ubuntu | Intel | :heavy_check_mark: |
Raspbian | ARM | :heavy_check_mark: |
Win x64 | Intel | :heavy_check_mark: |
When attempting to use lazysodium-java on an M1 mac (running MacOS Big Sur), the loading of the library within the jar file is resulting in the following error:
It looks like a recent checkin was made to handle that. Is there any chance of cutting a new release or patch that would work the the M1 mac?