Change timing output: We don't have "exponents" here, curves are

[openssl.git] / FAQ

diff --git a/FAQ b/FAQ
index 8fafbb2a6b180413839d3648523d5bd9b87cedeb..4702d6ac9b00950e7eb8a4ed96b633efc926dfe7 100644 (file)
--- a/FAQ
+++ b/FAQ
@@ -31,7 +31,7 @@ OpenSSL  -  Frequently Asked Questions
 
 * Why does the linker complain about undefined symbols?
 * Why does the OpenSSL test fail with "bc: command not found"?
-* Why does the OpenSSL test fail with "bc: 1 no implemented" or similar?
+* Why does the OpenSSL test fail with "bc: 1 no implemented"?
 * Why does the OpenSSL compilation fail on Alpha True64 Unix?
 * Why does the OpenSSL compilation fail with "ar: command not found"?
 * Why does the OpenSSL compilation fail on Win32 with VC++?
@@ -116,17 +116,8 @@ A number of Linux and *BSD distributions include OpenSSL.
 
 * Why aren't tools like 'autoconf' and 'libtool' used?
 
-autoconf is a nice tool, but is unfortunately very Unix-centric.
-Although one can come up with solution to have ports keep in track,
-there's also some work needed for that, and can be quite painful at
-times.  If there was a 'autoconf'-like tool that generated perl
-scripts or something similarly general, it would probably be used
-in OpenSSL much earlier.
-
-libtool has repeatadly been reported by some members of the OpenSSL
-development and others to be a pain to use.  So far, those in the
-development team who have said anything about this have expressed
-a wish to avoid libtool for that reason.
+autoconf will probably be used in future OpenSSL versions. If it was
+less Unix-centric, it might have been used much earlier.
 
 
 [LEGAL] =======================================================================
@@ -324,13 +315,11 @@ You didn't install "bc", the Unix calculator.  If you want to run the
 tests, get GNU bc from ftp://ftp.gnu.org or from your OS distributor.
 
 
-* Why does the OpenSSL test fail with "bc: 1 no implemented" or similar?
+* Why does the OpenSSL test fail with "bc: 1 no implemented"?
 
 On some SCO installations or versions, bc has a bug that gets triggered
 when you run the test suite (using "make test").  The message returned is
-"bc: 1 not implemented".  You may run into something similar on FreeBSD
-(version 4.2 has been reported), where the message is "Failed! bc: tmp.bntest
-3: print statement" or something similar.
+"bc: 1 not implemented".
 
 The best way to deal with this is to find another implementation of bc
 and compile/install it.  GNU bc (see http://www.gnu.org/software/software.html