the README file specific to your operating system, since this 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 specific information for your
+system. (Unixware users should use the svr4.sh hint file.)
+
=head1 Space Requirements
The complete perl5 source tree takes up about 7 MB of disk space. The
Configure will figure out various things about your system. Some
things Configure will figure out for itself, other things it will ask
you about. To accept the default, just press RETURN. The default
-is almost always ok.
+is almost always ok. At any Configure prompt, you can type &-d
+and Configure will use the defaults from then on.
After it runs, Configure will perform variable substitution on all the
*.SH files and offer to run make depend.
If you want to use your old config.sh but override some of the items
with command line options, you need to use B<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
statically, you can either choose this when Configure prompts you or
you can use the Configure command line option -Uusedl.
+If you are willing to accept all the defaults, and you want terse
+output, you can run
+
+ sh Configure -des
+
+For my Solaris system, I usually use
+
+ sh Configure -Dprefix=/opt/perl -Doptimize='-xpentium -xO4' -des
+
=head2 GNU-style configure
If you prefer the GNU-style configure command line interface, you can
sh Configure -Doptimize='-g'
-This will do two things: First, it will force compilation to use
-cc -g so that you can use your system's debugger on the executable.
-Second, it will add a -DDEBUGGING to your ccflags variable in
+This will do two independent things: First, it will force compilation
+to use cc -g so that you can use your system's debugger on the
+executable. (Note: Your system may actually require something like
+cc -g2. Check you man pages for cc(1) and also any hint file for your
+system.) Second, it will add -DDEBUGGING to your ccflags variable in
config.sh so that you can use B<perl -D> to access perl's internal
-state. Note, however, that Configure will only add -DDEBUGGING by
+state. (Note: Configure will only add -DDEBUGGING by
default if you are not reusing your old config.sh. If you want to
reuse your old config.sh, then you can just edit it and change the
optimize and ccflags variables by hand and then propagate your changes
-as shown in L<"Propagating your changes to config.sh"> below.
+as shown in L<"Propagating your changes to config.sh"> below.)
+
+You can actually specify -g and -DDEBUGGING independently, but usually
+it's convenient to have both.
If you are using a shared libperl, see the warnings about multiple
versions of perl under L<Building a shared libperl.so Perl library>.
sh Configure -Dccflags='-Drand=random -Dsrand=srandom'
-or by adding -Drand=random and -Dsrandom=srandom to your ccflags
-at the appropriate Configure prompt. (You may also have to adjust
-Configure's guess for 'randbits' as well.)
+or by adding -Drand=random and -Dsrand=srandom to your ccflags
+at the appropriate Configure prompt. (Note: Although this worked for
+me, it might not work for you if your system's header files give
+different prototypes for rand() and random() or srand() and srandom().)
+
+You should also run Configure interactively to verify that a hint file
+doesn't inadvertently override your ccflags setting. (Hints files
+shouldn't do that, but some might.)
=head2 What if it doesn't work?
Solaris, and you are using GNU as and GNU ld, you may need to add
-B/bin/ (for SunOS) or -B/usr/ccs/bin/ (for Solaris) to your
$ccflags, $ldflags, and $lddlflags so that the system's versions of as
-and ld are used. Alternatively, you can use the GCC_EXEC_PREFIX
+and ld are used. Note that the trailing '/' is required.
+Alternatively, you can use the GCC_EXEC_PREFIX
environment variable to ensure that Sun's as and ld are used. Consult
your gcc documentation for further information on the -B option and
the GCC_EXEC_PREFIX variable.
may also wish to add a symbolic link /usr/local/bin/perl so that
scripts can still start with #!/usr/local/bin/perl.
+If you are installing a development subversion, you probably ought to
+seriously consider using a separate directory, since development
+subversions may not have all the compatibility wrinkles ironed out
+yet.
+
=head1 Coexistence with perl4
You can safely install perl5 even if you want to keep perl4 around.
=head1 LAST MODIFIED
-$Id: INSTALL,v 1.11 1997/03/26 19:08:06 doughera Released $
+$Id: INSTALL,v 1.15 1997/04/16 20:49:24 doughera Exp $
projects / p5sagit/p5-mst-13.2.git / blobdiff