=head1 Space Requirements
-The complete perl5 source tree takes up about 35 MB of disk space.
-After completing make, it takes up roughly 50 MB, though the actual
+The complete perl5 source tree takes up about 40 MB of disk space.
+After completing make, it takes up roughly 60 MB, though the actual
total is likely to be quite system-dependent. The installation
-directories need something on the order of 30 MB, though again that
+directories need something on the order of 35 MB, though again that
value is system-dependent.
=head1 Start with a Fresh Distribution
make depend
make
-=item config.over
+=item config.over and config.arch
-You can also supply a shell script config.over to over-ride Configure's
-guesses. It will get loaded up at the very end, just before config.sh
-is created. You have to be careful with this, however, as Configure
-does no checking that your changes make sense.
+You can also supply a shell script config.over to over-ride
+Configure's guesses. It will get loaded up at the very end, just
+before config.sh is created. You have to be careful with this,
+however, as Configure does no checking that your changes make sense.
+This file is usually good for site-specific customizations.
+
+There is also another file that, if it exists, is loaded before the
+config.over, called config.arch. This file is intended to be per
+architecture, not per site, and usually it's the architecture-specific
+hints file that creates the config.arch.
=item config.h
subdirectory. Especially Porting/Glossary should come in handy.
Ports for other systems may also be available. You should check out
-http://www.perl.com/CPAN/ports for current information on ports to
+http://www.cpan.org/ports for current information on ports to
various other operating systems.
If you plan to port Perl to a new architecture study carefully the
open("...|"). All these mean that Perl is trying to run some
external program.
+=item Timing problems
+
+Several tests in the test suite check timing functions, such as
+sleep(), and see if they return in a reasonable amount of time.
+If your system is quite busy and doesn't return quickly enough,
+these tests might fail. If possible, try running the tests again with
+the system under a lighter load. These tests include F<t/op/alarm.t>,
+F<ext/Time/HiRes/HiRes.t>, and F<lib/Benchmark.t>.
+
=item Out of memory
On some systems, particularly those with smaller amounts of RAM, some