summaryrefslogtreecommitdiff
path: root/FAQ
diff options
context:
space:
mode:
authorRichard Levitte <levitte@openssl.org>2002-08-15 10:50:42 +0000
committerRichard Levitte <levitte@openssl.org>2002-08-15 10:50:42 +0000
commit5e947727a90ec45f66de50091eadf286830321f0 (patch)
tree4e97b53b32786cf91911dc50b90a023c6a3537a4 /FAQ
parentd7bd58cf365627019ac9898ee4c916748672792c (diff)
Add a FAQ entry for yet another bc failure.
PR: 199
Diffstat (limited to 'FAQ')
-rw-r--r--FAQ12
1 files changed, 12 insertions, 0 deletions
diff --git a/FAQ b/FAQ
index e7642707bd..28027fdcac 100644
--- a/FAQ
+++ b/FAQ
@@ -36,6 +36,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: stack empty"?
* Why does the OpenSSL compilation fail on Alpha Tru64 Unix?
* Why does the OpenSSL compilation fail with "ar: command not found"?
* Why does the OpenSSL compilation fail on Win32 with VC++?
@@ -402,6 +403,17 @@ 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 test fail with "bc: stack empty"?
+
+On some DG/ux versions, bc seems to have a too small stack for calculations
+that the OpenSSL bntest throws at it. This gets triggered when you run the
+test suite (using "make test"). The message returned is "bc: stack empty".
+
+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 Tru64 Unix?
On some Alpha installations running Tru64 Unix and Compaq C, the compilation