-
-
Notifications
You must be signed in to change notification settings - Fork 311
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
Supplied libzkgroup.so does not work #413
Comments
It might be worth re-building the lib file from source then. I made a wiki page detailing how to deal with this library file. If you have any questions or feel it could be improved, please let me know. |
Thanks for your answer. However, I do not really understand how that should make a difference. Your wiki-page says "Do note that signal-cli already comes pre-bundled with the linux x86_64 version of zkgroup so if you are on that platform then you should be able to use signal-cli with no issues." |
To be clear, what OS are you using? If its not linux, then any .so file won't work and you'll have to build the right library file. I'm still new to the zkgroup stuff aswell, the wiki page is what worked for me and some other people. As a last option I think its worth a shot manually building the x86_64 library. However AsamK knows more about this than I do, he'll probably be online in half a day's time from now if you're willing to wait. |
This is the OS I'm using: CentOS Linux release 7.5.1804 (Core) |
If I try to update the profile (updateProfile) I get another error, which also mentions "zkgroup". Exception in thread "main" java.lang.NoClassDefFoundError: Could not initialize class org.signal.zkgroup.internal.Native |
Yeah I recall a number of things depend on the zkgroup stuff despite not being "group" related. I had one of these too and when I got zkgroup working it disappeared, so don't worry too much about it. Your OS is linux so I think it would be fine. I guess you can either wait for AsamK or you can try compile a new library file in the meantime. |
Looks like the bundled zkgroup lib was built with glibc 2.18 or newer (it requires a symbol with version GLIBC_2.18). |
ldd --version says 2.17 |
Ok, I managed to compile a new libzkgroup.so for i686, and... IT WORKS! |
any manual how you did that? (Cargo build, and than what the next action, copy something conpiled to some directory?) |
This repo has pre-compiled libraries: https://github.com/exquo/signal-libs-build. See the commands in the instructions section for adding them to signal-cli. |
Same here... Tried to specify glibc 2.18 path:
|
Sounds like your OS has an even earlier version of glibc (<=2.18). I don't think you can practicably specify or install a newer glibc version manually. To use the libraries on that system, you'll need to compile them on it. See instructions in the wiki |
The supplied libzkgroup.so file does not seem to work.
The output of uname --m is x86_64, so it should be the correct version.
If I extract this libzkgroup.so from the supplied jar and put it in the java lib path, it still doesn't work.
No matter what I do, I still get the following message:
WARN org.asamk.signal.Main - WARNING: Support for new group V2 is disabled, because the required native library dependency is missing: libzkgroup
java --version says:
openjdk 11.0.9.1 2020-11-04 LTS
OpenJDK Runtime Environment 18.9 (build 11.0.9.1+1-LTS)
OpenJDK 64-Bit Server VM 18.9 (build 11.0.9.1+1-LTS, mixed mode, sharing)
The text was updated successfully, but these errors were encountered: