commit 8f0da580686d7a40eb710809ee2500eb57ba7830
from: Omar Polo <op@omarpolo.com>
date: Thu Jan 21 13:12:35 2021 UTC

mention the configure script and how to link to a local libtls

commit - 597ddf6ca821ab0a47c0a4f978fd79d67d40fcec
commit + 8f0da580686d7a40eb710809ee2500eb57ba7830
blob - c3bc947800e336127800777b96f0d922c50ce908
blob + aa67019fd680e63bb4986b803b55dc5dedcf9464
--- README.md
+++ README.md
@@ -40,6 +40,9 @@ The build is as simple as
 
     make
 
+If the configure scripts fails to pick up something, please open an
+isuse or notify me via email.
+
 To install execute:
 
     make install
@@ -60,7 +63,24 @@ and then run it with something along the lines of
 
 ellipses used for brevity.
 
+#### Local libretls
 
+This is **NOT** recommended, please try to port LibreSSL/LibreTLS to
+your distribution of choice or use docker instead.
+
+However, it's possible to link `gmid` to locally-installed libtls
+quite easily.  (It's how I test gmid on Fedora, for instance)
+
+Let's say you have compiled and installed libressl in `$LIBRESSL`,
+then you can build `gmid` with
+
+    ./configure CFLAGS="-I$LIBRESSL/include" \
+                LDFLAGS="$LIBRESSL/lib/libtls.a -lssl -lcrypto"
+    make
+
+(Fedora requires also `-lpthread` for some reason)
+
+
 ## Architecture/Security considerations
 
 gmid is composed by two processes: a listener and an executor.  The