summaryrefslogtreecommitdiffstats
path: root/FAQ
diff options
context:
space:
mode:
authorAndy Polyakov <appro@openssl.org>2005-11-09 19:43:40 +0000
committerAndy Polyakov <appro@openssl.org>2005-11-09 19:43:40 +0000
commit65613f23bafeb26145b86b2649d0f554411bb052 (patch)
treeb00f4b076202fbccde323d9678f6e31dd10454c4 /FAQ
parent4f92a764f169f3bd844bc248a45464a7bd83df4b (diff)
Mention PROBLEMS in FAQ.
Diffstat (limited to 'FAQ')
-rw-r--r--FAQ21
1 files changed, 17 insertions, 4 deletions
diff --git a/FAQ b/FAQ
index 889eb0ac43..fda3323f25 100644
--- a/FAQ
+++ b/FAQ
@@ -49,6 +49,7 @@ OpenSSL - Frequently Asked Questions
* Why does OpenBSD-i386 build fail on des-586.s with "Unimplemented segment type"?
* Why does the OpenSSL test suite fail in sha512t on x86 CPU?
* Why does compiler fail to compile sha512.c?
+* Test suite still fails, what to do?
[PROG] Questions about programming with OpenSSL
@@ -655,6 +656,18 @@ the module in question. The recommendation is to disable SHA-512 by
adding no-sha512 to ./config [or ./Configure] command line. Another
possible alternative might be to switch to GCC.
+* Test suite still fails, what to do?
+
+Another common reason for failure to complete some particular test is
+simply bad code generated by a buggy component in toolchain or deficiency
+in run-time environment. There are few cases documented in PROBLEMS file,
+consult it for possible workaround before you beat the drum. Even if you
+don't find solution or even mention there, do reserve for possibility of
+a compiler bug. Compiler bugs might appear in rather bizarre ways, they
+never make sense, and tend to emerge when you least expect them. In order
+to identify one, drop optimization level, e.g. by editing CFLAG line in
+top-level Makefile, recompile and re-run the test.
+
[PROG] ========================================================================
* Is OpenSSL thread-safe?
@@ -687,10 +700,10 @@ your application must link against the same by which OpenSSL was
built. If you are using MS Visual C++ (Studio) this can be changed
by:
-1. Select Settings... from the Project Menu.
-2. Select the C/C++ Tab.
-3. Select "Code Generation from the "Category" drop down list box
-4. Select the Appropriate library (see table below) from the "Use
+ 1. Select Settings... from the Project Menu.
+ 2. Select the C/C++ Tab.
+ 3. Select "Code Generation from the "Category" drop down list box
+ 4. Select the Appropriate library (see table below) from the "Use
run-time library" drop down list box. Perform this step for both
your debug and release versions of your application (look at the
top left of the settings panel to change between the two)