SIPP-OpenSSL-Perl Installation Guide

View INSTALL of perl
The basic steps to build and install perl5 on a Unix system with all the defaults are: The basic steps to build and install perl5 on a Unix system with all the defaults are:
#rm -f config.sh Policy.sh
sh Configure -de (default Compile by gcc)
#make
#make test
#make install
Each of these is explained in further detail below. The above commands will install Perl to /usr/local (or some other platform-specific directory -- see the appropriate file in hints/.) If that's not okay with you, can run Configure interactively and use
#rm -f config.sh Policy.sh
#sh Configure
#make
#make test
#make install # You may also wish to add these: (cd /usr/include && h2ph *.h sys/*.h) (installhtml --help) (cd pod && make tex &&) or you can use some of the Configure options described below. For information on what's new in this release, see the pod/perldelta.pod file. For more detailed information about specific changes, see the Changes file. In addition to this file, check if there is a README file specific to your operating system, since it may provide additional or different instructions for building Perl. If there is a hint file for your system (in the hints/ directory) you should also read that hint file for even more information. (Unixware users should use the svr4.sh or the svr5.sh hint file.)

ReInstall
If you have built extensions (i.e. modules that include C code) using an earlier version of Perl, you will need to rebuild and reinstall those extensions. If you have built perl before, you should clean out the build directory with the command make distclean or make realclean The only difference between the two is that make distclean also removes your old config.sh and Policy.sh files. The results of a Configure run are stored in the config.sh and Policy.sh files. If you are upgrading from a previous version of perl, or if you change systems or compilers or make other significant changes, or if you are experiencing difficulties building perl, you should probably not re-use your old config.sh. Simply remove it rm -f config.sh If you wish to use your old config.sh, be especially attentive to the version and architecture-specific questions and answers. For example, the default directory for architecture-dependent library modules includes the version name. By default, Configure will reuse your old name (e.g. /opt/perl/lib/i86pc-solaris/5.003) even if you're running Configure for a different version, e.g. 5.004. Yes, Configure should probably check and correct for this, but it doesn't. Similarly, if you used a shared libperl.so (see below) with version numbers, you will probably want to adjust them as well. Also, be careful to check your architecture name. For example, some Linux distributions use i386, while others may use i486. If you build it yourself, Configure uses the output of the arch command, which might be i586 or i686 instead. If you pick up a precompiled binary, or compile extensions on different systems, they might not all agree on the architecture name. In short, if you wish to use your old config.sh, I recommend running Configure interactively rather than blindly accepting the defaults. If your reason to reuse your old config.sh is to save your particular installation choices, then you can probably achieve the same effect by using the Policy.sh file. See the section on L<"Site-wide Policy settings"> below. If you wish to start with a fresh distribution, you also need to remove any old Policy.sh files you may have with rm -f Policy.sh