From 3aad40d38f3cba359f78f81dd27b420d19aa45b7 Mon Sep 17 00:00:00 2001
From: Laurent Bercot
At all times, ./configure --help provides the list of sysdeps
you need to provide a --with-sysdep-* option for. As of
-skalibs-2.9.1.0, there is only one sysdep in this case:
+skalibs-2.9.3.0, there is only one sysdep in this case:
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 /usr/bin:/bin, which is usually safe.
+ When compiling natively, skalibs probes the build system for sysdeps, +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 K, if you want to +enforce the value V, you can use --enable-sysdep-K=V +as a configure option. +
+ ++(This is similar to the ac_cv_foobar_K=V environment +variable mechanism in autotools.) +
+ ++ When cross-compiling, there are a few sysdeps +that cannot be autodetected and have to be provided manually on the +command line. The devurandom sysdep, which encodes the existence of +a functional /dev/urandom device on the target, is one of those. +--enable-sysdep-devurandom=yes tells skalibs to assume that there is +such a device it can rely on for random number generation. +
+