2 INSTALLATION ON THE UNIX PLATFORM
3 ---------------------------------
5 [For instructions for compiling OpenSSL on Windows systems, see INSTALL.W32].
7 To install OpenSSL, you will need:
11 * a supported Unix operating system
16 If you want to just get on with it, do:
18 $ ./config [if this fails, go to step 1b below]
24 This will build and install OpenSSL in the default location, which is (for
25 historical reasons) /usr/local/ssl. If you want to install it anywhere else,
26 do this after running `./config':
28 $ perl util/ssldir.pl /new/install/path
30 There are several options to ./config to customize the build:
32 rsaref Build with RSADSI's RSAREF toolkit.
33 no-asm Build with no assembler code.
34 386 Use the 80386 instruction set only (the default x86 code is
35 more efficient, but requires at least a 486).
37 If anything goes wrong, follow the detailed instructions below. If your
38 operating system is not (yet) supported by OpenSSL, see the section on
39 porting to a new system.
41 Installation in Detail
42 ----------------------
44 1a. Configure OpenSSL for your operation system automatically:
48 This guesses at your operating system (and compiler, if necessary) and
49 configures OpenSSL based on this guess. Check the first line of output to
50 see if it guessed correctly. If it did not get it correct or you want to
51 use a different compiler then go to step 1b. Otherwise go to step 2.
53 1b. Configure OpenSSL for your operating system manually
55 OpenSSL knows about a range of different operating system, hardware and
56 compiler combinations. To see the ones it knows about, run
60 Pick a suitable name from the list that matches your system. For most
61 operating systems there is a choice between using "cc" or "gcc". When
62 you have identified your system (and if necessary compiler) use this name
63 as the argument to ./Configure. For example, a "linux-elf" user would
66 $ ./Configure linux-elf
68 If your system is not available, you will have to edit the Configure
69 program and add the correct configuration for your system.
71 Configure creates the Makefile.ssl from Makefile.org and defines
72 various macros in crypto/opensslconf.h (generated from
73 crypto/opensslconf.h.in).
75 2. Set the install directory
77 If the install directory will be the default of /usr/local/ssl, skip to
78 the next stage. Otherwise, run
80 $ perl util/ssldir.pl /new/install/path
82 This configures the installation location into the "install" target of
83 the top-level Makefile, and also updates some defines in an include file
84 so that the default certificate directory is under the proper
85 installation directory. It also updates a few utility files used in the
88 3. Build OpenSSL by running:
92 This will build the OpenSSL libraries (libcrypto.a and libssl.a) and the
93 OpenSSL binary ("openssl"). The libraries will be built in the top-level
94 directory, and the binary will be in the "apps" directory.
96 4. After a successful build, the libraries should be tested. Run:
101 (The first line makes the test certificates in the "certs" directory
102 accessable via an hash name, which is required for some of the tests).
104 5. If everything tests ok, install OpenSSL with
108 This will create the installation directory (if it does not exist) and
109 then create the following subdirectories:
111 bin Contains the openssl binary and a few other
113 include Contains the header files needed if you want to
114 compile programs with libcrypto or libssl.
115 lib Contains the library files themselves and the
116 OpenSSL configuration file "openssl.cnf".
117 certs Initially empty, this is the default location
118 for certificate files.
119 private Initially empty, this is the default location
120 for private key files.
123 NOTE: The header files used to reside directly in the include
124 directory, but have now been moved to include/openssl so that
125 OpenSSL can co-exist with other libraries which use some of the
126 same filenames. This means that applications that use OpenSSL
127 should now use C preprocessor directives of the form
129 #include <openssl/ssl.h>
131 instead of "#include <ssl.h>", which was used with library versions
132 up to OpenSSL 0.9.2b.
134 If you install a new version of OpenSSL over an old library version,
135 you should delete the old header files in the include directory.
137 Compatibility issues:
139 * COMPILING existing applications
141 To compile an application that uses old filenames -- e.g.
142 "#include <ssl.h>" --, it will usually be enough to find
143 the CFLAGS definition in the application's Makefile and
144 add a C option such as
146 -I/usr/local/ssl/include/openssl
150 But don't delete the existing -I option that points to
151 the ..../include directory! Otherwise, OpenSSL header files
152 could not #include each other.
154 * WRITING applications
156 To write an application that is able to handle both the new
157 and the old directory layout, so that it can still be compiled
158 with library versions up to OpenSSL 0.9.2b without bothering
159 the user, you can proceed as follows:
161 - Always use the new filename of OpenSSL header files,
162 e.g. #include <openssl/ssl.h>.
164 - Create a directory "incl" that contains only a symbolic
165 link named "openssl", which points to the "include" directory
167 For example, your application's Makefile might contain the
168 following rule, if OPENSSLDIR is a pathname (absolute or
169 relative) of the directory where OpenSSL resides:
173 cd $(OPENSSLDIR) # Check whether the directory really exists
174 -ln -s `cd $(OPENSSLDIR); pwd`/include incl/openssl
176 You will have to add "incl/openssl" to the dependencies
177 of those C files that include some OpenSSL header file.
179 - Add "-Iincl" to your CFLAGS.
181 With these additions, the OpenSSL header files will be available
182 under both name variants if an old library version is used:
183 Your application can reach them under names like <openssl/foo.h>,
184 while the header files still are able to #include each other
185 with names of the form <foo.h>.
189 --------------------------------------------------------------------------------
190 The orignal Unix build instructions from SSLeay follow.
191 Note: some of this may be out of date and no longer applicable
192 --------------------------------------------------------------------------------
194 # When bringing the SSLeay distribution back from the evil intel world
195 # of Windows NT, do the following to make it nice again under unix :-)
196 # You don't normally need to run this.
197 sh util/fixNT.sh # This only works for NT now - eay - 21-Jun-1996
199 # If you have perl, and it is not in /usr/local/bin, you can run
200 perl util/perlpath.pl /new/path
201 # and this will fix the paths in all the scripts. DO NOT put
202 # /new/path/perl, just /new/path. The build
203 # environment always run scripts as 'perl perlscript.pl' but some of the
204 # 'applications' are easier to usr with the path fixed.
206 # Edit crypto/cryptlib.h, tools/c_rehash, and Makefile.ssl
207 # to set the install locations if you don't like
208 # the default location of /usr/local/ssl
210 perl util/ssldir.pl /new/ssl/home
211 # if you have perl, or by hand if not.
213 # If things have been stuffed up with the sym links, run
214 make -f Makefile.ssl links
215 # This will re-populate lib/include with symlinks and for each
216 # directory, link Makefile to Makefile.ssl
218 # Setup the machine dependent stuff for the top level makefile
219 # and some select .h files
220 # If you don't have perl, this will bomb, in which case just edit the
221 # top level Makefile.ssl
222 ./Configure 'system type'
224 # The 'Configure' command contains default configuration parameters
225 # for lots of machines. Configure edits 5 lines in the top level Makefile
226 # It modifies the following values in the following files
227 Makefile.ssl CC CFLAG EX_LIBS BN_MULW
228 crypto/des/des.h DES_LONG
229 crypto/des/des_locl.h DES_PTR
230 crypto/md2/md2.h MD2_INT
231 crypto/rc4/rc4.h RC4_INT
232 crypto/rc4/rc4_enc.c RC4_INDEX
233 crypto/rc2/rc2.h RC2_INT
234 crypto/bf/bf_locl.h BF_INT
235 crypto/idea/idea.h IDEA_INT
236 crypto/bn/bn.h BN_LLONG (and defines one of SIXTY_FOUR_BIT,
237 SIXTY_FOUR_BIT_LONG, THIRTY_TWO_BIT,
238 SIXTEEN_BIT or EIGHT_BIT)
239 Please remember that all these files are actually copies of the file with
240 a .org extention. So if you change crypto/des/des.h, the next time
241 you run Configure, it will be runover by a 'configured' version of
242 crypto/des/des.org. So to make the changer the default, change the .org
243 files. The reason these files have to be edited is because most of
244 these modifications change the size of fundamental data types.
245 While in theory this stuff is optional, it often makes a big
246 difference in performance and when using assember, it is importaint
247 for the 'Bignum bits' match those required by the assember code.
248 A warning for people using gcc with sparc cpu's. Gcc needs the -mv8
249 flag to use the hardware multiply instruction which was not present in
250 earlier versions of the sparc CPU. I define it by default. If you
251 have an old sparc, and it crashes, try rebuilding with this flag
252 removed. I am leaving this flag on by default because it makes
253 things run 4 times faster :-)
255 # clean out all the old stuff
258 # Do a make depend only if you have the makedepend command installed
259 # This is not needed but it does make things nice when developing.
262 # make should build everything
265 # fix up the demo certificate hash directory if it has been stuffed up.
274 # It is worth noting that all the applications are built into the one
275 # program, ssleay, which is then has links from the other programs
277 # The applicatons can be built by themselves, just don't define the
278 # 'MONOLITH' flag. So to build the 'enc' program stand alone,
279 gcc -O2 -Iinclude apps/enc.c apps/apps.c libcrypto.a
281 # Other useful make options are
283 # which generate a 'makefile.one' file which will build the complete
284 # SSLeay distribution with temp. files in './tmp' and 'installable' files
287 # Have a look at running
288 perl util/mk1mf.pl help
289 # this can be used to generate a single makefile and is about the only
290 # way to generate makefiles for windows.
292 # There is actually a final way of building SSLeay.
293 gcc -O2 -c -Icrypto -Iinclude crypto/crypto.c
294 gcc -O2 -c -Issl -Iinclude ssl/ssl.c
295 # and you now have the 2 libraries as single object files :-).
296 # If you want to use the assember code for your particular platform
297 # (DEC alpha/x86 are the main ones, the other assember is just the
298 # output from gcc) you will need to link the assember with the above generated
299 # object file and also do the above compile as
300 gcc -O2 -DBN_ASM -c -Icrypto -Iinclude crypto/crypto.c
302 This last option is probably the best way to go when porting to another
303 platform or building shared libraries. It is not good for development so
304 I don't normally use it.
306 To build shared libararies under unix, have a look in shlib, basically
307 you are on your own, but it is quite easy and all you have to do
308 is compile 2 (or 3) files.
310 For mult-threading, have a read of doc/threads.doc. Again it is quite
311 easy and normally only requires some extra callbacks to be defined
313 The examples for solaris and windows NT/95 are in the mt directory.
319 IRIX 5.x will build as a 32 bit system with mips1 assember.
320 IRIX 6.x will build as a 64 bit system with mips3 assember. It conforms
321 to n32 standards. In theory you can compile the 64 bit assember under
322 IRIX 5.x but you will have to have the correct system software installed.