{"schema":"libjg2-1", "vpath":"/git/", "avatar":"/git/avatar/", "alang":"", "gen_ut":1757458957, "reponame":"openssl", "desc":"OpenSSL", "owner": { "name": "Andy Green", "email": "andy@warmcat.com", "md5": "c50933ca2aa61e0fe2c43d46bb6b59cb" },"url":"https://warmcat.com/repo/openssl", "f":3, "items": [ {"schema":"libjg2-1", "cid":"fb0bf05c449685037b11fc0982defeef", "oid":{ "oid": "6ea3d1836be7e3cbaceeafa1d824b4f770df3fb0", "alias": []},"blobname": "INSTALL", "blob": "\n INSTALLATION ON THE UNIX PLATFORM\n ---------------------------------\n\n [Installation on DOS (with djgpp), Windows, OpenVMS, MacOS (before MacOS X)\n and NetWare is described in INSTALL.DJGPP, INSTALL.W32, INSTALL.VMS,\n INSTALL.MacOS and INSTALL.NW.\n \n This document describes installation on operating systems in the Unix\n family.]\n\n To install OpenSSL, you will need:\n\n * make\n * Perl 5\n * an ANSI C compiler\n * a development environment in form of development libraries and C\n header files\n * a supported Unix operating system\n\n Quick Start\n -----------\n\n If you want to just get on with it, do:\n\n $ ./config\n $ make\n $ make test\n $ make install\n\n [If any of these steps fails, see section Installation in Detail below.]\n\n This will build and install OpenSSL in the default location, which is (for\n historical reasons) /usr/local/ssl. If you want to install it anywhere else,\n run config like this:\n\n $ ./config --prefix\u003d/usr/local --openssldir\u003d/usr/local/openssl\n\n\n Configuration Options\n ---------------------\n\n There are several options to ./config (or ./Configure) to customize\n the build:\n\n --prefix\u003dDIR Install in DIR/bin, DIR/lib, DIR/include/openssl.\n\t Configuration files used by OpenSSL will be in DIR/ssl\n or the directory specified by --openssldir.\n\n --openssldir\u003dDIR Directory for OpenSSL files. If no prefix is specified,\n the library files and binaries are also installed there.\n\n no-threads Don't try to build with support for multi-threaded\n applications.\n\n threads Build with support for multi-threaded applications.\n This will usually require additional system-dependent options!\n See \u0022Note on multi-threading\u0022 below.\n\n no-zlib Don't try to build with support for zlib compression and\n decompression.\n\n zlib Build with support for zlib compression/decompression.\n\n zlib-dynamic Like \u0022zlib\u0022, but has OpenSSL load the zlib library dynamically\n when needed. This is only supported on systems where loading\n of shared libraries is supported. This is the default choice.\n\n no-shared Don't try to create shared libraries.\n\n shared In addition to the usual static libraries, create shared\n libraries on platforms where it's supported. See \u0022Note on\n shared libraries\u0022 below.\n\n no-asm Do not use assembler code.\n\n 386 Use the 80386 instruction set only (the default x86 code is\n more efficient, but requires at least a 486). Note: Use\n compiler flags for any other CPU specific configuration,\n e.g. \u0022-m32\u0022 to build x86 code on an x64 system.\n\n no-sse2\tExclude SSE2 code pathes. Normally SSE2 extension is\n\t\tdetected at run-time, but the decision whether or not the\n\t\tmachine code will be executed is taken solely on CPU\n\t\tcapability vector. This means that if you happen to run OS\n\t\tkernel which does not support SSE2 extension on Intel P4\n\t\tprocessor, then your application might be exposed to\n\t\t\u0022illegal instruction\u0022 exception. There might be a way\n\t\tto enable support in kernel, e.g. FreeBSD kernel can be\n\t\tcompiled with CPU_ENABLE_SSE, and there is a way to\n\t\tdisengage SSE2 code pathes upon application start-up,\n\t\tbut if you aim for wider \u0022audience\u0022 running such kernel,\n\t\tconsider no-sse2. Both 386 and no-asm options above imply\n\t\tno-sse2.\n\n no-\u003ccipher\u003e Build without the specified cipher (bf, cast, des, dh, dsa,\n hmac, md2, md5, mdc2, rc2, rc4, rc5, rsa, sha).\n The crypto/\u003ccipher\u003e directory can be removed after running\n \u0022make depend\u0022.\n\n -Dxxx, -lxxx, -Lxxx, -fxxx, -mXXX, -Kxxx These system specific options will\n be passed through to the compiler to allow you to\n define preprocessor symbols, specify additional libraries,\n library directories or other compiler options.\n\n\n Installation in Detail\n ----------------------\n\n 1a. Configure OpenSSL for your operation system automatically:\n\n $ ./config [options]\n\n This guesses at your operating system (and compiler, if necessary) and\n configures OpenSSL based on this guess. Run ./config -t to see\n if it guessed correctly. If you want to use a different compiler, you\n are cross-compiling for another platform, or the ./config guess was\n wrong for other reasons, go to step 1b. Otherwise go to step 2.\n\n On some systems, you can include debugging information as follows:\n\n $ ./config -d [options]\n\n 1b. Configure OpenSSL for your operating system manually\n\n OpenSSL knows about a range of different operating system, hardware and\n compiler combinations. To see the ones it knows about, run\n\n $ ./Configure\n\n Pick a suitable name from the list that matches your system. For most\n operating systems there is a choice between using \u0022cc\u0022 or \u0022gcc\u0022. When\n you have identified your system (and if necessary compiler) use this name\n as the argument to ./Configure. For example, a \u0022linux-elf\u0022 user would\n run:\n\n $ ./Configure linux-elf [options]\n\n If your system is not available, you will have to edit the Configure\n program and add the correct configuration for your system. The\n generic configurations \u0022cc\u0022 or \u0022gcc\u0022 should usually work on 32 bit\n systems.\n\n Configure creates the file Makefile.ssl from Makefile.org and\n defines various macros in crypto/opensslconf.h (generated from\n crypto/opensslconf.h.in).\n\n 2. Build OpenSSL by running:\n\n $ make\n\n This will build the OpenSSL libraries (libcrypto.a and libssl.a) and the\n OpenSSL binary (\u0022openssl\u0022). The libraries will be built in the top-level\n directory, and the binary will be in the \u0022apps\u0022 directory.\n\n If \u0022make\u0022 fails, look at the output. There may be reasons for\n the failure that aren't problems in OpenSSL itself (like missing\n standard headers). If it is a problem with OpenSSL itself, please\n report the problem to \u003copenssl-bugs@openssl.org\u003e (note that your\n message will be recorded in the request tracker publicly readable\n via http://www.openssl.org/support/rt.html and will be forwarded to a\n public mailing list). Include the output of \u0022make report\u0022 in your message.\n Please check out the request tracker. Maybe the bug was already\n reported or has already been fixed.\n\n [If you encounter assembler error messages, try the \u0022no-asm\u0022\n configuration option as an immediate fix.]\n\n Compiling parts of OpenSSL with gcc and others with the system\n compiler will result in unresolved symbols on some systems.\n\n 3. After a successful build, the libraries should be tested. Run:\n\n $ make test\n\n If a test fails, look at the output. There may be reasons for\n the failure that isn't a problem in OpenSSL itself (like a missing\n or malfunctioning bc). If it is a problem with OpenSSL itself,\n try removing any compiler optimization flags from the CFLAG line\n in Makefile.ssl and run \u0022make clean; make\u0022. Please send a bug\n report to \u003copenssl-bugs@openssl.org\u003e, including the output of\n \u0022make report\u0022 in order to be added to the request tracker at\n http://www.openssl.org/support/rt.html.\n\n 4. If everything tests ok, install OpenSSL with\n\n $ make install\n\n This will create the installation directory (if it does not exist) and\n then the following subdirectories:\n\n certs Initially empty, this is the default location\n for certificate files.\n man/man1 Manual pages for the 'openssl' command line tool\n man/man3 Manual pages for the libraries (very incomplete)\n misc Various scripts.\n private Initially empty, this is the default location\n for private key files.\n\n If you didn't choose a different installation prefix, the\n following additional subdirectories will be created:\n\n bin Contains the openssl binary and a few other \n utility programs. \n include/openssl Contains the header files needed if you want to\n compile programs with libcrypto or libssl.\n lib Contains the OpenSSL library files themselves.\n\n Use \u0022make install_sw\u0022 to install the software without documentation,\n and \u0022install_docs_html\u0022 to install HTML renditions of the manual\n pages.\n\n Package builders who want to configure the library for standard\n locations, but have the package installed somewhere else so that\n it can easily be packaged, can use\n\n $ make INSTALL_PREFIX\u003d/tmp/package-root install\n\n (or specify \u0022--install_prefix\u003d/tmp/package-root\u0022 as a configure\n option). The specified prefix will be prepended to all\n installation target filenames.\n\n\n NOTE: The header files used to reside directly in the include\n directory, but have now been moved to include/openssl so that\n OpenSSL can co-exist with other libraries which use some of the\n same filenames. This means that applications that use OpenSSL\n should now use C preprocessor directives of the form\n\n #include \u003copenssl/ssl.h\u003e\n\n instead of \u0022#include \u003cssl.h\u003e\u0022, which was used with library versions\n up to OpenSSL 0.9.2b.\n\n If you install a new version of OpenSSL over an old library version,\n you should delete the old header files in the include directory.\n\n Compatibility issues:\n\n * COMPILING existing applications\n\n To compile an application that uses old filenames -- e.g.\n \u0022#include \u003cssl.h\u003e\u0022 --, it will usually be enough to find\n the CFLAGS definition in the application's Makefile and\n add a C option such as\n\n -I/usr/local/ssl/include/openssl\n\n to it.\n\n But don't delete the existing -I option that points to\n the ..../include directory! Otherwise, OpenSSL header files\n could not #include each other.\n\n * WRITING applications\n\n To write an application that is able to handle both the new\n and the old directory layout, so that it can still be compiled\n with library versions up to OpenSSL 0.9.2b without bothering\n the user, you can proceed as follows:\n\n - Always use the new filename of OpenSSL header files,\n e.g. #include \u003copenssl/ssl.h\u003e.\n\n - Create a directory \u0022incl\u0022 that contains only a symbolic\n link named \u0022openssl\u0022, which points to the \u0022include\u0022 directory\n of OpenSSL.\n For example, your application's Makefile might contain the\n following rule, if OPENSSLDIR is a pathname (absolute or\n relative) of the directory where OpenSSL resides:\n\n incl/openssl:\n \t-mkdir incl\n \tcd $(OPENSSLDIR) # Check whether the directory really exists\n \t-ln -s `cd $(OPENSSLDIR); pwd`/include incl/openssl\n\n You will have to add \u0022incl/openssl\u0022 to the dependencies\n of those C files that include some OpenSSL header file.\n\n - Add \u0022-Iincl\u0022 to your CFLAGS.\n\n With these additions, the OpenSSL header files will be available\n under both name variants if an old library version is used:\n Your application can reach them under names like \u003copenssl/foo.h\u003e,\n while the header files still are able to #include each other\n with names of the form \u003cfoo.h\u003e.\n\n\n Note on multi-threading\n -----------------------\n\n For some systems, the OpenSSL Configure script knows what compiler options\n are needed to generate a library that is suitable for multi-threaded\n applications. On these systems, support for multi-threading is enabled\n by default; use the \u0022no-threads\u0022 option to disable (this should never be\n necessary).\n\n On other systems, to enable support for multi-threading, you will have\n to specify at least two options: \u0022threads\u0022, and a system-dependent option.\n (The latter is \u0022-D_REENTRANT\u0022 on various systems.) The default in this\n case, obviously, is not to include support for multi-threading (but\n you can still use \u0022no-threads\u0022 to suppress an annoying warning message\n from the Configure script.)\n\n\n Note on shared libraries\n ------------------------\n\n Shared libraries have certain caveats. Binary backward compatibility\n can't be guaranteed before OpenSSL version 1.0. The only reason to\n use them would be to conserve memory on systems where several programs\n are using OpenSSL.\n\n For some systems, the OpenSSL Configure script knows what is needed to\n build shared libraries for libcrypto and libssl. On these systems,\n the shared libraries are currently not created by default, but giving\n the option \u0022shared\u0022 will get them created. This method supports Makefile\n targets for shared library creation, like linux-shared. Those targets\n can currently be used on their own just as well, but this is expected\n to change in future versions of OpenSSL.\n\n Note on random number generation\n --------------------------------\n\n Availability of cryptographically secure random numbers is required for\n secret key generation. OpenSSL provides several options to seed the\n internal PRNG. If not properly seeded, the internal PRNG will refuse\n to deliver random bytes and a \u0022PRNG not seeded error\u0022 will occur.\n On systems without /dev/urandom (or similar) device, it may be necessary\n to install additional support software to obtain random seed.\n Please check out the manual pages for RAND_add(), RAND_bytes(), RAND_egd(),\n and the FAQ for more information.\n\n Note on support for multiple builds\n -----------------------------------\n\n OpenSSL is usually built in its source tree. Unfortunately, this doesn't\n support building for multiple platforms from the same source tree very well.\n It is however possible to build in a separate tree through the use of lots\n of symbolic links, which should be prepared like this:\n\n\tmkdir -p objtree/\u0022`uname -s`-`uname -r`-`uname -m`\u0022\n\tcd objtree/\u0022`uname -s`-`uname -r`-`uname -m`\u0022\n\t(cd $OPENSSL_SOURCE; find . -type f) | while read F; do\n\t\tmkdir -p `dirname $F`\n\t\trm -f $F; ln -s $OPENSSL_SOURCE/$F $F\n\t\techo $F '-\u003e' $OPENSSL_SOURCE/$F\n\tdone\n\tmake -f Makefile.org clean\n\n OPENSSL_SOURCE is an environment variable that contains the absolute (this\n is important!) path to the OpenSSL source tree.\n\n Also, operations like 'make update' should still be made in the source tree.\n","s":{"c":1757458957,"u": 527}} ],"g": 4793,"chitpc": 0,"ehitpc": 0,"indexed":0 , "ab": 1, "si": 0, "db":0, "di":0, "sat":0, "lfc": "0000"}