[openssl-commits] [web] master update

[Matt Caswell]

The branch master has been updated
       via  138e3301b632ea41392651378493c96fe2b93915 (commit)
       via  58537db2776a93629226b580be19917ecfa4725a (commit)
      from  f8be505ebf987ff74075122e2914b1be8bb3fef5 (commit)


- Log -----------------------------------------------------------------
commit 138e3301b632ea41392651378493c96fe2b93915
Author: Matt Caswell <matt at openssl.org>
Date:   Tue Jun 13 13:02:13 2017 +0100

    Remove reference to deleted PROBLEMS file
    
    Reviewed-by: Andy Polyakov <appro at openssl.org>
    Reviewed-by: Rich Salz <rsalz at openssl.org>
    (Merged from https://github.com/openssl/openssl/pull/17)

commit 58537db2776a93629226b580be19917ecfa4725a
Author: Matt Caswell <matt at openssl.org>
Date:   Tue Jun 13 12:57:33 2017 +0100

    Remove MAC-OS/X FAQ entries
    
    The issues discussed were resolved in 0.9.8f according to Andy Polyakov in
    PR#15
    
    Reviewed-by: Andy Polyakov <appro at openssl.org>
    Reviewed-by: Rich Salz <rsalz at openssl.org>
    (Merged from https://github.com/openssl/openssl/pull/17)

-----------------------------------------------------------------------

Summary of changes:
 docs/faq-4-build.txt | 29 +----------------------------
 1 file changed, 1 insertion(+), 28 deletions(-)

diff --git a/docs/faq-4-build.txt b/docs/faq-4-build.txt
index b02cb1f..efa754f 100644
--- a/docs/faq-4-build.txt
+++ b/docs/faq-4-build.txt
@@ -86,30 +86,6 @@ relevant updates in packages up to and including 0.9.6b.
 A possible way around this is to persuade Red Hat to produce a non-US
 version of Red Hat Linux.
 
-* Why does the OpenSSL compilation fail on MacOS X?
-
-If the failure happens when trying to build the "openssl" binary, with
-a large number of undefined symbols, it's very probable that you have
-OpenSSL 0.9.6b delivered with the operating system (you can find out by
-running '/usr/bin/openssl version') and that you were trying to build
-OpenSSL 0.9.7 or newer.  The problem is that the loader ('ld') in
-MacOS X has a misfeature that's quite difficult to go around.
-Look in the file PROBLEMS for a more detailed explanation and for possible
-solutions.
-
-* Why does the OpenSSL test suite fail on MacOS X?
-
-If the failure happens when running 'make test' and the RC4 test fails,
-it's very probable that you have OpenSSL 0.9.6b delivered with the
-operating system (you can find out by running '/usr/bin/openssl version')
-and that you were trying to build OpenSSL 0.9.6d.  The problem is that
-the loader ('ld') in MacOS X has a misfeature that's quite difficult to
-go around and has linked the programs "openssl" and the test programs
-with /usr/lib/libcrypto.dylib and /usr/lib/libssl.dylib instead of the
-libraries you just built.
-Look in the file PROBLEMS for a more detailed explanation and for possible
-solutions.
-
 * Why does the OpenSSL test suite fail in BN_sqr test [on a 64-bit platform]?
 
 Failure in BN_sqr test is most likely caused by a failure to configure the
@@ -147,10 +123,7 @@ possible alternative might be to switch to GCC.
 * Test suite still fails, what to do?
 
 Another common reason for test failures is bugs in the toolchain
-or run-time environment.  Known cases of this are documented in the
-PROBLEMS file, please review it before you beat the drum. Even if you
-don't find anything in that file, please do consider the possibility
-of a compiler bug. Compiler bugs often appear in rather bizarre ways,
+or run-time environment. Compiler bugs often appear in rather bizarre ways,
 they never make sense, and tend to emerge when you least expect
 them. One thing to try is to reduce the level of optimization (such
 as by editing the CFLAG variable line in the top-level Makefile),