From 7d51240251f8226089ab1618831fde50b5e9e641 Mon Sep 17 00:00:00 2001
From: Laurent Bercot <ska-skaware@skarnet.org>
Date: Fri, 4 Nov 2016 16:58:26 +0000
Subject:  Remove obsolete flags from flags.html, prepare for 2.4.0.1

---
 doc/flags.html | 34 ----------------------------------
 1 file changed, 34 deletions(-)

(limited to 'doc/flags.html')

diff --git a/doc/flags.html b/doc/flags.html
index 5dfcffd..ad39b4b 100644
--- a/doc/flags.html
+++ b/doc/flags.html
@@ -241,40 +241,6 @@ relevant networking functions if and only if the target architecture supports it
 This is the default, and it is safe.
 </p>
 
-<a name="forcedevr"><h3> --enable-force-devr </h3></a>
-
-<p>
- If this option is set, then the automatic sysdeps tests will assume the
-target architecture has a working <tt>/dev/random</tt> and will skip
-its autodetection.
-</p>
-
-<p>
- Otherwise, <tt>/dev/random</tt> will be autodetected
-and tested; if entropy generation is low on the host, the compilation
-process might hang for several minutes. It is safe to leave this flag
-clear; it should only be set to speed up the compilation process in a
-known environment or for testing purposes.
-</p>
-
-<p>
- If skalibs is being cross-compiled, this flag obviously has no effect:
-the presence of a working <tt>/dev/random</tt> is read from the user-provided
-sysdeps.
-</p>
-
-<a name="forcedevr"><h3> --enable-egd=<em>path</em> </h3></a>
-
-<p>
- If you set this option, then the <a href="librandom/">librandom</a> functions
-will assume the presence of an EGD daemon listening on <em>path</em>,
-and use it to get random data.
-</p>
-
-<p>
- By default, skalibs will not include EGD support.
-</p>
-
 <a name="defaultpath"><h3> --with-default-path=<em>path</em> </h3></a>
 
 <p>
-- 
cgit v1.3.1