FAQ update to mention no-sha0 as possible workaround for Tru64 compiler bug.

Well, no-options seem to be busted in HEAD currently, which should/will be
fixed one way or another (see PR#989 for a possible alternative).

diff --git a/FAQ b/FAQ
index fd354b3b40234701678cf99aca1b818835cd84b7..12f3d24d16d0d6a06205a1eecd3d3c87622d7a16 100644 (file)
--- a/FAQ
+++ b/FAQ
@@ -473,6 +473,10 @@ This will only compile sha_dgst.c with -O0, the rest with the optimization
 level chosen by the configuration process.  When the above is done, do the
 test and installation and you're set.
 
+3. Reconfigure the toolkit with no-sha0 option to leave out SHA0. It 
+should not be used and is not used in SSL/TLS nor any other recognized
+protocol in either case.
+
 
 * Why does the OpenSSL compilation fail with "ar: command not found"?