X-Git-Url: https://git.openssl.org/?p=openssl.git;a=blobdiff_plain;f=INSTALL;h=e18fdfcf55e2bdfac69104d0aadb4c269be314c3;hp=d394bf8a7b9eac0cc96d14069e34ba6673443211;hb=5810a5f4c767ba68185e38fa2c5709425c1903a8;hpb=78414a6a897db42c9bcf06aa21c705811ab33921;ds=sidebyside diff --git a/INSTALL b/INSTALL index d394bf8a7b..e18fdfcf55 100644 --- a/INSTALL +++ b/INSTALL @@ -1,3 +1,154 @@ +Installing OpenSSL on Unix +-------------------------- + +[For instructions for compiling OpenSSL on Windows systems, see +INSTALL.W32]. + +To install OpenSSL, you will need: + + * Perl + * C compiler + * A supported operating system + +Quick Start +----------- + +If you want to just get on with it, do: + + sh config [if this fails, go to step 1b below] + make -f Makefile.ssl links + make + make rehash + make test + make install + +This will build and install OpenSSL in the default location, which is +/usr/local/ssl. If you want to install it anywhere else, do this +after running ./Configure : + + perl util/ssldir.pl /new/install/path + +If anything goes wrong, follow the detailed instructions below. If +your operating system is not (yet) supported by OpenSSL, see the +section on porting to a new system. + +Installation in Detail +---------------------- + + 1a. Configure OpenSSL for your operation system automatically + + Run + + sh config + + This guesses at your operating system (and compiler, if + necessary) and configures OpenSSL based on this guess. Check the + first line of output 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. + + 1b. Configure OpenSSL for your operating system manually + + OpenSSL knows about a range of different operating system, hardware + and compiler combinations. To see the ones it knows about, run + + ./Configure + + Pick a suitable name from the list that matches your system. For + most operating systems there is a choice between using "cc" or + "gcc". + + When you have identified your system (and if necessary compiler) + use this name as the argument to ./Configure. For example, a + "linux-elf" user would run: + + ./Configure linux-elf + + If your system is not available, you will have to edit the Configure + program and add the correct configuration for your system. + + Configure configures various files by converting an existing .org + file into the real file. If you edit any files, remember that if + a corresponding .org file exists them the next time you run + ./Configure your changes will be lost when the file gets + re-created from the .org file. The files that are created from + .org files are: + + Makefile.ssl + crypto/des/des.h + crypto/des/des_locl.h + crypto/md2/md2.h + crypto/rc4/rc4.h + crypto/rc4/rc4_enc.c + crypto/rc2/rc2.h + crypto/bf/bf_locl.h + crypto/idea/idea.h + crypto/bn/bn.h + + 2. Set the install directory + + If the install directory will be the default of /usr/local/ssl, + skip to the next stage. Otherwise, run + + perl util/ssldir.pl /new/install/path + + This configures the installation location into the "install" + target of the top-level Makefile, and also updates some defines + in an include file so that the default certificate directory is + under the proper installation directory. It also updates a few + utility files used in the build process. + + 3. Build OpenSSL + + Now run + + make + + This will build the OpenSSL libraries (libcrypto.a and libssl.a) + and the OpenSSL binary ("openssl"). The libraries will be built + in the top-level directory, and the binary will be in the "apps" + directory. + + 4. After a successful build, the libraries should be tested. Run + + make rehash + make test + + (The first line makes the test certificates in the "certs" + directory accessable via an hash name, which is required for some + of the tests). + + 5. If everything tests ok, install OpenSSL with + + make install + + This will create the installation directory (if it does not + exist) and then create the following subdirectories: + + bin Contains the openssl binary and a few other utility + programs. It also contains symbolic links so + that openssl commands can be accessed directly + (e.g. so that "s_client" can be used instead of + "openssl s_client"). + certs Initially empty, this is the default location + for certificate files. + include Contains the header files needed if you want to + compile programs with libcrypto or libssl. + lib Contains the library files themselves and the + OpenSSL configuration file "openssl.cnf". + private Initially empty, this is the default location + for private key files. + +---------------------------------------------------------------------- + +Additional Compilation Notes +---------------------------- + +These notes come from SSLeay 0.9.1 and cover some more advanced +facilities (such as building a single makefile for use on Windows +systems). + + # Installation of SSLeay. # It depends on perl for a few bits but those steps can be skipped and # the top level makefile edited by hand @@ -126,3 +277,8 @@ The examples for solaris and windows NT/95 are in the mt directory. have fun eric 25-Jun-1997 + +IRIX 5.x will build as a 32 bit system with mips1 assember. +IRIX 6.x will build as a 64 bit system with mips3 assember. It conforms +to n32 standards. In theory you can compile the 64 bit assember under +IRIX 5.x but you will have to have the correct system software installed.