directories ahead of those in APPLLIB_EXP by using any of the standard
run-time methods: $PERLLIB, $PERL5LIB, -I, use lib, etc.
-=item USE_SITECUSTOMIZE
+=item usesitecustomize
Run-time customization of @INC can be enabled with:
sh Configure -Dusesitecustomize
-Which will define USE_SITECUSTOMIZE and $Config{usesitecustomize}.
-When enabled, make perl run F<$sitelibexp/sitecustomize.pl> before
+which will define USE_SITECUSTOMIZE and $Config{usesitecustomize}.
+When enabled, this makes perl run F<$sitelibexp/sitecustomize.pl> before
anything else. This script can then be set up to add additional
entries to @INC.
by hand to see if it makes any difference. If individual tests
bomb, you can run them by hand, e.g.,
- ./perl op/groups.t
+ cd t ; ./perl -MTestInit op/groups.t
Another way to get more detailed information about failed tests and
individual subtests is to cd to the t directory and run
- ./perl harness
+ cd t ; ./perl harness <list of tests>
(this assumes that most basic tests succeed, since harness uses
-complicated constructs). For extension and library tests you
-need a little bit more: you need to setup your environment variable
-PERL_CORE to a true value (like "1"), and you need to supply the
-right Perl library path:
+complicated constructs). If no list of tests is provided, harness
+will run all tests.
- setenv PERL_CORE 1
- ./perl -I../lib ../ext/Socket/Socket.t
- ./perl -I../lib ../lib/less.t
-
-(For csh-like shells on UNIX; adjust appropriately for other platforms.)
You should also read the individual tests to see if there are any helpful
comments that apply to your system. You may also need to setup your
shared library path if you get errors like:
Note: One possible reason for errors is that some external programs
may be broken due to the combination of your environment and the way
-B<make test> exercises them. For example, this may happen if you have
+'make test' exercises them. For example, this may happen if you have
one or more of these environment variables set: LC_ALL LC_CTYPE
LC_COLLATE LANG. In some versions of UNIX, the non-English locales
are known to cause programs to exhibit mysterious errors.
these tests might fail. If possible, try running the tests again
with the system under a lighter load. These timing-sensitive
and load-sensitive tests include F<t/op/alarm.t>,
-F<ext/Time/HiRes/HiRes.t>, F<lib/Benchmark.t>,
+F<ext/Time/HiRes/t/HiRes.t>, F<ext/threads/shared/t/waithires.t>,
+F<ext/threads/shared/t/stress.t>, F<lib/Benchmark.t>,
F<lib/Memoize/t/expmod_t.t>, and F<lib/Memoize/t/speed.t>.
+You might also experience some failures in F<t/op/stat.t> if you build
+perl on an NFS filesystem, if the remote clock and the system clock are
+different.
+
=item Out of memory
On some systems, particularly those with smaller amounts of RAM, some
Try stopping other jobs on the system and then running the test by itself:
- cd t; ./perl op/pat.t
+ cd t; ./perl -MTestInit op/pat.t
to see if you have any better luck. If your perl still fails this
test, it does not necessarily mean you have a broken perl. This test
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 re-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. 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, but Configure uses the output of the arch
-command, which might be 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.
+you are experiencing difficulties building perl, you should not re-use
+your old config.sh.
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"> above. 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
+settings"> above.
=head1 Minimizing the Perl installation
can type B<perldoc perl> to use the supplied perldoc script. This is
sometimes useful for finding things in the library modules.
-Under UNIX, you can produce a documentation book in postscript form,
-along with its table of contents, by going to the pod/ subdirectory and
-running (either):
-
- ./roffitall -groff # If you have GNU groff installed
- ./roffitall -psroff # If you have psroff
-
-This will leave you with two postscript files ready to be printed.
-(You may need to fix the roffitall command to use your local troff
-set-up.)
-
-Note that you must have performed the installation already before running
-the above, since the script collects the installed files to generate
-the documentation.
-
=head1 AUTHOR
Original author: Andy Dougherty doughera@lafayette.edu , borrowing very
https://perl5.git.perl.org / perl5.git / blobdiff