glibc version requirement for linux

exquo 2021-06-17 11:24:35 +00:00
parent 5626959268
commit 721b5775d8

@ -1,7 +1,7 @@
The latest libsignal-service requires [libsignal-client](https://github.com/signalapp/libsignal-client), a native (rust) library, for the protocol implementation. Additionally for the new v2 groups libsignal-service requires [libzkgroup](https://github.com/signalapp/zkgroup), another native (rust) library.
You need to use the library files that are compiled for your CPU architecture and operating system.
Do note that signal-cli already comes pre-bundled with the linux (gnu libc) x86_64 version of zkgroup and libsignal-service, so if you are on that platform then you should be able to use signal-cli with no issues.
Do note that signal-cli already comes pre-bundled with the linux (with a recent enough gnu libc, see [#643](https://github.com/AsamK/signal-cli/issues/643)) x86_64 version of zkgroup and libsignal-service, so if you are on that platform then you should be able to use signal-cli with no issues.
# libsignal-client
### Building libsignal-client yourself
@ -63,4 +63,4 @@ If your `java.library.path` doesn't have any usable paths or you wish to not use
JAVA_LIBRARY_PATH="-Djava.library.path=/your/java/library/path"
exec "$JAVACMD" "$JAVA_LIBRARY_PATH" "$@"
```
Make sure to place your `.dylib`/`.so`/`.dll` file in that folder. Be aware that this method isn't ideal since if you rebuild signal-cli, then the script may be regenerated and you'll need to set this again.
Make sure to place your `.dylib`/`.so`/`.dll` file in that folder. Be aware that this method isn't ideal since if you rebuild signal-cli, then the script may be regenerated and you'll need to set this again.