Mention PROBLEMS in FAQ.
This commit is contained in:
parent
4f92a764f1
commit
65613f23ba
1 changed files with 17 additions and 4 deletions
21
FAQ
21
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 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 the OpenSSL test suite fail in sha512t on x86 CPU?
|
||||||
* Why does compiler fail to compile sha512.c?
|
* Why does compiler fail to compile sha512.c?
|
||||||
|
* Test suite still fails, what to do?
|
||||||
|
|
||||||
[PROG] Questions about programming with OpenSSL
|
[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
|
adding no-sha512 to ./config [or ./Configure] command line. Another
|
||||||
possible alternative might be to switch to GCC.
|
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] ========================================================================
|
[PROG] ========================================================================
|
||||||
|
|
||||||
* Is OpenSSL thread-safe?
|
* 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
|
built. If you are using MS Visual C++ (Studio) this can be changed
|
||||||
by:
|
by:
|
||||||
|
|
||||||
1. Select Settings... from the Project Menu.
|
1. Select Settings... from the Project Menu.
|
||||||
2. Select the C/C++ Tab.
|
2. Select the C/C++ Tab.
|
||||||
3. Select "Code Generation from the "Category" drop down list box
|
3. Select "Code Generation from the "Category" drop down list box
|
||||||
4. Select the Appropriate library (see table below) from the "Use
|
4. Select the Appropriate library (see table below) from the "Use
|
||||||
run-time library" drop down list box. Perform this step for both
|
run-time library" drop down list box. Perform this step for both
|
||||||
your debug and release versions of your application (look at the
|
your debug and release versions of your application (look at the
|
||||||
top left of the settings panel to change between the two)
|
top left of the settings panel to change between the two)
|
||||||
|
|
Loading…
Reference in a new issue