Commit d9248e57 authored by Andy Polyakov's avatar Andy Polyakov
Browse files

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).
parent 0b52f89b

FAQ

+4 −0
Original line number Diff line number Diff line
@@ -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"?