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

dlopen failed: library "liboqs-jni.so" not found #15

Closed
Ammar-Ishfaq opened this issue Aug 5, 2024 · 2 comments
Closed

dlopen failed: library "liboqs-jni.so" not found #15

Ammar-Ishfaq opened this issue Aug 5, 2024 · 2 comments

Comments

@Ammar-Ishfaq
Copy link

Hi there. could you please share this fix?. I've already got the liboqs file there.
FATAL EXCEPTION: main Process: com.example.liboqstestapp, PID: 31062 java.lang.UnsatisfiedLinkError: dlopen failed: library "liboqs-jni.so" not found at java.lang.Runtime.loadLibrary0(Runtime.java:1082) at java.lang.Runtime.loadLibrary0(Runtime.java:1003) at java.lang.System.loadLibrary(System.java:1661) at com.example.liboqs.Common.loadNativeLibrary(Common.java:31) at com.example.liboqs.KEMs.<clinit>(KEMs.java:12) at com.example.liboqstestapp.MainActivity.onCreate(MainActivity.java:49)

@Hatzen
Copy link
Owner

Hatzen commented Aug 5, 2024

Hi, next time please consider providing more context and necessary information (what environment, which modifications/Branch, how to reproduce).
I assume you checked out the master Branch and tried to run the app in the emulator?
Please consider reading the Readme

There seems to be an issue (or further configuration) with compiling for 32 Bit abis like x86 and arm-7 (#2 and #3). Because of this the local emulator (x86) might not compile as no .so file is provided.

So Emulator wont run because of not so easy (unrealistic/impossible) issues with the liboqs changes for android are needed.

Overall this repository is more a proof of concept, as the algorithms are not updated and may provide broken alogrithms.
I am not aware if the finalist of NISTs did change since releasing this repo.

The CI Part was stalled as you can read further here.
#13

2 links ahead young could find out that The fork of this repo probably resolves this issue

@Ammar-Ishfaq
Copy link
Author

Thank you for your response. I've checked the forked and it's working well.

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