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).
This commit is contained in:
Andy Polyakov 2005-01-09 20:42:33 +00:00
parent 0b52f89b81
commit d9248e5780

4
FAQ
View File

@ -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 level chosen by the configuration process. When the above is done, do the
test and installation and you're set. 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"? * Why does the OpenSSL compilation fail with "ar: command not found"?