summaryrefslogtreecommitdiffstats
path: root/lib/libssl/src/FAQ
diff options
context:
space:
mode:
authormarkus <markus@openbsd.org>2002-09-14 11:18:01 +0000
committermarkus <markus@openbsd.org>2002-09-14 11:18:01 +0000
commitcf5de1f602bfe31a1de0d5bcba280f0bf0a50ae2 (patch)
tree2658bb71397039b6e8ea6265a0bfe5a109de2a64 /lib/libssl/src/FAQ
parentspaces (diff)
downloadwireguard-openbsd-cf5de1f602bfe31a1de0d5bcba280f0bf0a50ae2.tar.xz
wireguard-openbsd-cf5de1f602bfe31a1de0d5bcba280f0bf0a50ae2.zip
merge with openssl-0.9.7-stable-SNAP-20020911,
new minor for libcrypto (_X509_REQ_print_ex) tested by miod@, pb@
Diffstat (limited to 'lib/libssl/src/FAQ')
-rw-r--r--lib/libssl/src/FAQ14
1 files changed, 13 insertions, 1 deletions
diff --git a/lib/libssl/src/FAQ b/lib/libssl/src/FAQ
index ee03d97676b..28027fdcacc 100644
--- a/lib/libssl/src/FAQ
+++ b/lib/libssl/src/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++?
@@ -64,7 +65,7 @@ OpenSSL - Frequently Asked Questions
* Which is the current version of OpenSSL?
The current version is available from <URL: http://www.openssl.org>.
-OpenSSL 0.9.6e was released on July 30, 2002.
+OpenSSL 0.9.6g was released on August 9, 2002.
In addition to the current stable release, you can also access daily
snapshots of the OpenSSL development version at <URL:
@@ -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