From 721b5775d8232e9e61fa706853a53df2cc205fc3 Mon Sep 17 00:00:00 2001
From: exquo <62397152+exquo@users.noreply.github.com>
Date: Thu, 17 Jun 2021 11:24:35 +0000
Subject: [PATCH] glibc version requirement for linux

---
 Provide-native-lib-for-libsignal.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/Provide-native-lib-for-libsignal.md b/Provide-native-lib-for-libsignal.md
index f784709..68e3a35 100644
--- a/Provide-native-lib-for-libsignal.md
+++ b/Provide-native-lib-for-libsignal.md
@@ -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.
\ No newline at end of file
+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.