summaryrefslogtreecommitdiffstats
path: root/FAQ
diff options
context:
space:
mode:
authorRichard Levitte <levitte@openssl.org>2001-02-14 07:45:59 +0000
committerRichard Levitte <levitte@openssl.org>2001-02-14 07:45:59 +0000
commit1417f2dccbaba7390d231056c99d38a5200124b8 (patch)
tree9ccd0c97f2b2067737ac2b9557796c8fe076610a /FAQ
parentf2e5ca84d4d218a29e2c960d9b23a40d8236cd06 (diff)
Include the newly reported problem with bc on FreeBSD 4.2.
Diffstat (limited to 'FAQ')
-rw-r--r--FAQ19
1 files changed, 11 insertions, 8 deletions
diff --git a/FAQ b/FAQ
index 4de8bb8c1a..8fafbb2a6b 100644
--- 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"?
+* Why does the OpenSSL test fail with "bc: 1 no implemented" or similar?
* 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,14 +324,17 @@ 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"?
+* Why does the OpenSSL test fail with "bc: 1 no implemented" or similar?
-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". The best way to deal with this is to find another
-implementation of bc and compile/install it. For example, GNU bc (see
-http://www.gnu.org/software/software.html for download instructions) can
-be safely used.
+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.
+
+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
+for download instructions) can be safely used, for example.
* Why does the OpenSSL compilation fail on Alpha True64 Unix?