skalibs

commit d64a3751ca805c08bfda6a330d73a09e87e993c0
parent 56066894b7d14f71aeba8379f0d6e5961dee733e
Author: Laurent Bercot <ska-skaware@skarnet.org>
Date:   Tue, 27 Jun 2023 08:37:17 +0000

 Doc fix

Signed-off-by: Laurent Bercot <ska@appnovation.com>

Diffstat:
M
doc/flags.html
 | 
6
+++---

1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/doc/flags.html b/doc/flags.html
@@ -174,14 +174,14 @@ 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>
+<a name="sysdep"><h3> --with-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>
+enforce the value <em>V</em>, you can use <tt>--with-sysdep-<em>K</em>=<em>V</em></tt>
 as a configure option.
 </p>
 
@@ -195,7 +195,7 @@ variable mechanism in autotools.)
 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
+<tt>--with-sysdep-devurandom=yes</tt> tells skalibs to assume that there is
 such a device it can rely on for random number generation.
 </p>