---------------------------------
[See INSTALL.W32 for instructions for compiling OpenSSL on Windows systems,
- and INSTALL.VMS for installing on OpenVMS systems.]
+ INSTALL.VMS for installing on OpenVMS systems, and INSTALL.MacOS for
+ installing on MacOS, but not MacOS X, systems.]
To install OpenSSL, you will need:
This guesses at your operating system (and compiler, if necessary) and
configures OpenSSL based on this guess. Run ./config -t to see
- if it guessed correctly. If it did not get it correct or you want to
- use a different compiler then go to step 1b. Otherwise go to step 2.
+ if it guessed correctly. If you want to use a different compiler, you
+ are cross-compiling for another platform, or the ./config guess was
+ wrong for other reasons, go to step 1b. Otherwise go to step 2.
On some systems, you can include debugging information as follows:
If your system is not available, you will have to edit the Configure
program and add the correct configuration for your system. The
- generic configurations "cc" or "gcc" should usually work.
+ generic configurations "cc" or "gcc" should usually work on 32 bit
+ systems.
Configure creates the file Makefile.ssl from Makefile.org and
defines various macros in crypto/opensslconf.h (generated from
If "make" fails, please report the problem to <openssl-bugs@openssl.org>
(note that your message will be forwarded to a public mailing list).
- Include the output of "./config -t" and the OpenSSL version
- number in your message.
+ Include the output of "make report" in your message.
[If you encounter assembler error messages, try the "no-asm"
configuration option as an immediate fix.]
If a test fails, try removing any compiler optimization flags from
the CFLAGS line in Makefile.ssl and run "make clean; make". Please
send a bug report to <openssl-bugs@openssl.org>, including the
- output of "openssl version -a" and of the failed test.
+ output of "make report".
4. If everything tests ok, install OpenSSL with
projects / openssl.git / blobdiff