rm -f config.sh sh Configure make make test make install
Each of these is explained in further detail below.
mv config.sh config.sh.old
Then run Configure.
RETURN
. The default is almost always ok.
After it runs, Configure will perform variable substitution on all the *.SH files and offer to run make depend .
Configure supports a number of useful options. Run Configure -h to get a listing. To compile with gcc, for example, you can run
sh Configure -Dcc=gcc
This is the preferred way to specify gcc (or another alternative compiler) so that the hints files can set appropriate defaults.
If you want to use your old config.sh but override some of the items with command line options, you need to use Configure -O .
If you are willing to accept all the defaults, and you want terse output, you can run
sh Configure -des
By default, for most systems, perl will be installed in /usr/local/{bin, lib, man}. You can specify a different 'prefix' for the default installation directory, when Configure prompts you or by using the Configure command line option -Dprefix='/some/directory', e.g.
sh Configure -Dprefix=/opt/perl
If your prefix contains the string ``perl'', then the directories are simplified. For example, if you use prefix=/opt/perl, then Configure will suggest /opt/perl/lib instead of /usr/local/lib/perl5/.
By default, Configure will compile perl to use dynamic loading, if your system supports it. If you want to force perl to be compiled statically, you can either choose this when Configure prompts you or by using the Configure command line option -Uusedl.
In summary, here are the Configure command-line variables you can set to turn off each extension:
DB_File i_db DynaLoader (Must always be included) Fcntl (Always included by default) GDBM_File i_gdbm NDBM_File i_ndbm ODBM_File i_dbm POSIX useposix SDBM_File (Always included by default) Safe usesafe Socket d_socket
Thus to skip the NDBM_File extension, you can use
sh Configure -Ui_ndbm
Again, this is taken care of automatically if you don't have the ndbm library.
Of course, you may always run Configure interactively and select only the Extensions you want.
Finally, if you have dynamic loading (most modern Unix systems do) remember that these extensions do not increase the size of your perl executable, nor do they impact start-up time, so you probably might as well build all the ones that will work on your system.
CC=gcc ./configure
The configure script emulates several of the more common configure options. Try
./configure --help
for a listing.
Cross compiling is currently not supported.
Note: If your database header (.h) files are not in a directory normally searched by your C compiler, then you will need to include the appropriate -I/your/directory option when prompted by Configure. If your database library (.a) files are not in a directory normally searched by your C compiler and linker, then you will need to include the appropriate -L/your/directory option when prompted by Configure. See the examples below.
Specifically, when Configure prompts you for flags for your C compiler, you
should include -I/usr/local/include
.
When Configure prompts you for linker flags, you should include
-L/usr/local/lib
.
If you are using dynamic loading, then when Configure prompts you for
linker flags for dynamic loading, you should again include
-L/usr/local/lib
.
Again, this should all happen automatically. If you want to accept the defaults for all the questions and have Configure print out only terse messages, then you can just run
sh Configure -des
and Configure should include the GDBM_File extension automatically.
This should actually work if you have gdbm installed in any of (/usr/local, /opt/local, /usr/gnu, /opt/gnu, /usr/GNU, or /opt/GNU).
It is possible to specify this from the command line too (all on one line):
sh Configure -des \ -Dlocincpth="/usr/you/include" \ -Dloclibpth="/usr/you/lib"
locincpth
is a space-separated list of include directories to search. Configure will
automatically add the appropriate -I
directives.
loclibpth
is a space-separated list of library directories to search. Configure will
automatically add the appropriate -L
directives. If you have some libraries under /usr/local/
and others under
/usr/you
, then you have to include both, namely
sh Configure -des \ -Dlocincpth="/usr/you/include /usr/local/include" \ -Dloclibpth="/usr/you/lib /usr/local/lib"
By default, Configure uses the following directories for library files (archname is a string like sun4-sunos, determined by Configure)
/usr/local/lib/perl5/archname/5.002 /usr/local/lib/perl5/ /usr/local/lib/perl5/site_perl/archname /usr/local/lib/perl5/site_perl
and the following directories for manual pages:
/usr/local/man/man1 /usr/local/lib/perl5/man/man3
(Actually, Configure recognizes the SVR3-style /usr/local/man/l_man/man1 directories, if present, and uses those instead.) The module man pages are stuck in that strange spot so that they don't collide with other man pages stored in /usr/local/man/man3, and so that Perl's man pages don't hide system man pages. On some systems, man less would end up calling up Perl's less.pm module man page, rather than the less program.
If you specify a prefix that contains the string ``perl'', then the directory structure is simplified. For example, if you Configure with -Dprefix=/opt/perl, then the defaults are
/opt/perl/lib/archname/5.002 /opt/perl/lib /opt/perl/lib/site_perl/archname /opt/perl/lib/site_perl
/opt/perl/man/man1 /opt/perl/man/man3
The perl executable will search the libraries in the order given above.
The directories site_perl and site_perl/archname are empty, but are intended to be used for installing local or site-wide extensions. Perl will automatically look in these directories. Previously, most sites just put their local extensions in with the standard distribution.
In order to support using things like #!/usr/local/bin/perl5.002 after a later version is released, architecture-dependent libraries are stored in a version-specific directory, such as /usr/local/lib/perl5/archname/5.002/. In 5.000 and 5.001, these files were just stored in /usr/local/lib/perl5/archname/. If you will not be using 5.001 binaries, you can delete the standard extensions from the /usr/local/lib/perl5/archname/ directory. Locally-added extensions can be moved to the site_perl and site_perl/archname directories.
Again, these are just the defaults, and can be changed as you run Configure.
-Dinstallprefix=/foo
to simplify this.
Suppose you want to install perl under the /tmp/perl5 directory. You can edit config.sh and change all the install* variables to point to /tmp/perl5 instead of /usr/local/wherever . You could also set them all from the Configure command line. Or, you can automate this process by placing the following lines in a file config.over before you run Configure (replace /tmp/perl5 by a directory of your choice):
installprefix=/tmp/perl5 test -d $installprefix || mkdir $installprefix test -d $installprefix/bin || mkdir $installprefix/bin installarchlib=`echo $installarchlib | sed "s!$prefix!$installprefix!"` installbin=`echo $installbin | sed "s!$prefix!$installprefix!"` installman1dir=`echo $installman1dir | sed "s!$prefix!$installprefix!"` installman3dir=`echo $installman3dir | sed "s!$prefix!$installprefix!"` installprivlib=`echo $installprivlib | sed "s!$prefix!$installprefix!"` installscript=`echo $installscript | sed "s!$prefix!$installprefix!"` installsitelib=`echo $installsitelib | sed "s!$prefix!$installprefix!"` installsitearch=`echo $installsitearch | sed "s!$prefix!$installprefix!"`
Then, you can Configure and install in the usual way:
sh Configure -des make make test make install
# Set up config.over to install perl into a different directory, # e.g. /tmp/perl5 (see previous part). sh Configure -des make make test make install cd /tmp/perl5 tar cvf ../perl5-archive.tar . # Then, on each machine where you want to install perl, cd /usr/local # Or wherever you specified as $prefix tar xvf perl5-archive.tar
All the installation questions have been moved to the top, so you don't have to wait for them. Once you've handled them (and your C compiler & flags) you can type '&-d' at the next Configure prompt and Configure will use the defaults from then on.
If you find yourself trying obscure command line incantations and config.over tricks, I recommend you run Configure interactively instead. You'll probably save yourself time in the long run.
Several of the hint files contain additional important information. If you have any problems, it is a good idea to read the relevant hint file for further information. See hints/solaris_2.sh for an extensive example.
This is a common source of problems. If you change from cc to gcc , you should almost always remove your old config.sh.
If there are any problems, you can edit config.h directly. Beware, though, that the next time you run Configure , your changes will be lost.
optimize='-g'
before the ;;
. You can also edit cflags
directly, but beware that your changes will be lost the next time you run Configure
.
To change the C flags for all the files, edit config.sh
and change either $ccflags
or $optimize
, and then re-run sh Configure -S ; make depend
.
Configure will offer to do this step for you, so it isn't listed explicitly above.
If you can't compile successfully, try some of the following ideas.
-DCRIPPLED_CC
flag. (Just because you get no errors doesn't mean it compiled right!) This
simplifies some complicated expressions for compilers that get indigestion
easily. If that has no effect, try turning off optimization. If you have
missing routines, you probably need to add some library or other, or you
need to undefine some feature that Configure thought was there but is
defective or incomplete.
make minitest
to test your version of miniperl.
Genix may need to use libc rather than libc_s, or #undef VARARGS.
NCR Tower 32 (OS 2.01.01) may need -W2,-Sl,2000 and #undef MKDIR.
UTS may need one or more of -DCRIPPLED_CC , -K or -g , and undef LSTAT.
If you get syntax errors on '(', try -DCRIPPLED_CC.
Machines with half-implemented dbm routines will need to #undef I_ODBM
SCO prior to 3.2.4 may be missing dbmclose().
An upgrade to
3.2.4 that includes libdbm.nfs (which includes dbmclose())
may
be available.
If you get duplicates upon linking for malloc et al, say -DHIDEMYMALLOC.
If you get duplicate function definitions (a perl function has the same name as another function on your system) try -DEMBED.
If you get varags problems with gcc, be sure that gcc is installed correctly. When using gcc, you should probably have i_stdarg='define' and i_varags='undef' in config.sh. The problem is usually solved by running fixincludes correctly.
If you wish to use dynamic loading on SunOS or Solaris, and you have GNU as
and GNU ld installed, you may need to add -B/bin/
to your $ccflags
and $ldflags
so that the
system's versions of as and ld are used.
If you run into dynamic loading problems, check your setting of the LD_LIBRARY_PATH environment variable. Perl should build fine with LD_LIBRARY_PATH unset, though that may depend on details of your local set-up.
If Configure seems to be having trouble finding library functions, try not using nm extraction. You can do this from the command line with
sh Configure -Uusenm
./perl op/groups.t
NOTE
: one possible reason for errors is that some external programs may be
broken due to the combination of your environment and the way
make test
exercises them. This may happen for example if you have one or more of
these environment variables set:
LC_ALL LC_CTYPE LANG
. In certain UNIXes especially the non-English locales are known to cause
programs to exhibit mysterious errors. If you have any of the above
environment variables set, please try
setenv LC_ALL C
or LC_ALL=C;export LC_ALL>, for csh
-style and
Bourne
-style shells, respectively, from the command line and then retry make test
. If the tests then succeed, you may have a broken program that is
confusing the testing. Please run the troublesome test by hand as shown
above and see whether you can locate the program. Look for things like:
exec, `backquoted command`, system, open("|...")
or open("...|")
. All these mean that Perl is trying to run some external program.
If you want to see exactly what will happen without installing anything, you can run
./perl installperl -n ./perl installman -n
make install will install the following:
perl, perl5.nnn where nnn is the current release number. This will be a link to perl. suidperl, sperl5.nnn If you requested setuid emulation. a2p awk-to-perl translator cppstdin This is used by perl -P, if your cc -E can't read from stdin. c2ph, pstruct Scripts for handling C structures in header files. s2p sed-to-perl translator find2perl find-to-perl translator h2xs Converts C .h header files to Perl extensions. perlbug Tool to report bugs in Perl. perldoc Tool to read perl's pod documentation. pod2html, Converters from perl's pod documentation format pod2latex, and to other useful formats. pod2man
library files in $privlib and $archlib specified to Configure, usually under /usr/local/lib/perl5/. man pages in the location specified to Configure, usually something like /usr/local/man/man1. module in the location specified to Configure, usually man pages under /usr/local/lib/perl5/man/man3. pod/*.pod in $privlib/pod/.
Installperl will also create the library directories $siteperl
and $sitearch
listed in config.sh. Usually, these are
something like /usr/local/lib/perl5/site_perl/
/usr/local/lib/perl5/site_perl/$archname where $archname
is
something like sun4-sunos. These directories will be used for installing
extensions.
Perl's *.h header files and the libperl.a library are also installed under
$archlib
so that any user may later build new extensions even
if the Perl source is no longer available.
The libperl.a library is only needed for building new extensions and linking them statically into a new perl executable. If you will not be doing that, then you may safely delete $archlib/libperl.a after perl is installed.
make install may also offer to install perl in a ``standard'' location.
Most of the documentation in the pod/ directory is also available in HTML and LaTeX format. Type
cd pod; make html; cd ..
to generate the html versions, and
cd pod; make tex; cd ..
to generate the LaTeX versions.
The architecture-dependent files are stored in a version-specific directory (such as /usr/local/lib/perl5/sun4-sunos/5.002 ) so that they are still accessible. Note: perl5.000 and perl5.001 did not put their architecture-dependent libraries in a version-specific directory. They are simply in /usr/local/lib/perl5/$archname . If you will not be using 5.000 or 5.001, you may safely remove those files.
The standard library files in /usr/local/lib/perl5 should be useable by all versions of perl5.
Most extensions will probably not need to be recompiled to use with a newer version of perl. If you do run into problems, and you want to continue to use the old version of perl along with your extension, simply move those extension files to the appropriate version directory, such as /usr/local/lib/perl/archname/5.002 . Then perl5.002 will find your files in the 5.002 directory, and newer versions of perl will find your newer extension in the site_perl directory.
Some users may prefer to keep all versions of perl in completely separate directories. One convenient way to do this is by using a separate prefix for each version, such as
sh Configure -Dprefix=/opt/perl5.002
and adding /opt/perl5.002/bin to the shell PATH variable. Such users may also wish to add a symbolic link /usr/local/bin/perl so that scripts can still start with #!/usr/local/bin/perl.
By default, the perl5 libraries go into /usr/local/lib/perl5/ , so they don't override the perl4 libraries in /usr/local/lib/perl/ .
In your /usr/local/bin directory, you should have a binary named
perl4.036
. That will not be touched by the perl5 installation process. Most perl4
scripts should run just fine under perl5. However, if you have any scripts
that require perl4, you can replace the #!
line at the top of them by #!/usr/local/bin/perl4.036
(or whatever the appropriate pathname is).