That was misleading. The problem won't happen with 0.9.6a anyway.

[openssl.git] / FAQ

diff --git a/FAQ b/FAQ
index 8fafbb2a6b180413839d3648523d5bd9b87cedeb..ab74287977db95eca1b416ff2d317e2de0255206 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++?
@@ -324,13 +324,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