From 3aad40d38f3cba359f78f81dd27b420d19aa45b7 Mon Sep 17 00:00:00 2001
From: Laurent Bercot <ska-skaware@skarnet.org>
Date: Fri, 18 Sep 2020 09:35:43 +0000
Subject:  Prepare for 2.9.3.0

---
 doc/flags.html | 25 +++++++++++++++++++++++++
 1 file changed, 25 insertions(+)

(limited to 'doc/flags.html')

diff --git a/doc/flags.html b/doc/flags.html
index e6895ed..7aa8f95 100644
--- a/doc/flags.html
+++ b/doc/flags.html
@@ -174,5 +174,30 @@ often anyway).
  The default is <tt>/usr/bin:/bin</tt>, which is usually safe.
 </p>
 
+<a name="sysdep"><h3> --enable-sysdep-devurandom=yes </h3></a>
+
+<p>
+ When compiling natively, skalibs probes the build system for <em>sysdeps</em>,
+i.e. system-specific behaviours that influence the way skalibs must
+implement certain interfaces. This autodetection can be overriden on the
+configure command line: for a sysdep named <em>K</em>, if you want to
+enforce the value <em>V</em>, you can use <tt>--enable-sysdep-<em>K</em>=<em>V</em></tt>
+as a configure option.
+</p>
+
+<p>
+(This is similar to the <tt>ac_cv_foobar_<em>K</em>=<em>V</em></tt> environment
+variable mechanism in autotools.)
+</p>
+
+<p>
+ When <a href="crosscompile.html">cross-compiling</a>, there are a few sysdeps
+that <em>cannot</em> be autodetected and have to be provided manually on the
+command line. The <tt>devurandom</tt> sysdep, which encodes the existence of
+a functional <tt>/dev/urandom</tt> device on the target, is one of those.
+<tt>--enable-sysdep-devurandom=yes</tt> tells skalibs to assume that there is
+such a device it can rely on for random number generation.
+</p>
+
 </body>
 </html>
-- 
cgit v1.2.3