From: Richard Levitte <levitte@openssl.org>
Date: Thu, 15 Aug 2002 10:50:42 +0000 (+0000)
Subject: Add a FAQ entry for yet another bc failure.
X-Git-Tag: OpenSSL_0_9_7-beta4~195
X-Git-Url: https://git.librecmc.org/?a=commitdiff_plain;h=5e947727a90ec45f66de50091eadf286830321f0;p=oweals%2Fopenssl.git

Add a FAQ entry for yet another bc failure.
PR: 199
---

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