diff options
| author | Jarkko Hietaniemi <jhi@iki.fi> | 2015-11-16 21:00:27 -0500 |
|---|---|---|
| committer | Jarkko Hietaniemi <jhi@iki.fi> | 2015-11-17 11:24:17 -0500 |
| commit | fb034ed92b97457964b9c5566ffde039c0f0721e (patch) | |
| tree | dc6326f614f07f09f24138c38de5f9ffe068f07b /README.tru64 | |
| parent | 4451fd4ea2932e23705437d82f10e66970a22c3f (diff) | |
| download | perl-fb034ed92b97457964b9c5566ffde039c0f0721e.tar.gz | |
tru64: Freshen the section on required process data size limits.
Diffstat (limited to 'README.tru64')
| -rw-r--r-- | README.tru64 | 17 |
1 files changed, 10 insertions, 7 deletions
diff --git a/README.tru64 b/README.tru64 index d1714601ce..39cb27fa03 100644 --- a/README.tru64 +++ b/README.tru64 @@ -26,13 +26,16 @@ of the op/regexp and op/pat, or ext/Storable tests dumping core (the exact pattern of failures depending on the GCC release and optimization flags). -gcc 3.2.1 is known to work okay with Perl 5.8.0. However, when -optimizing the toke.c gcc likes to have a lot of memory, 256 megabytes -seems to be enough. The default setting of the process data section -in Tru64 should be one gigabyte, but some sites/setups might have -lowered that. The configuration process of Perl checks for too low -process limits, and lowers the optimization for the toke.c if -necessary, and also gives advice on how to raise the process limits. +Both the native cc and gcc seem to consume lots of memory when +building Perl. toke.c is a known trouble spot when optimizing: +256 megabytes of data section seems to be enough. Another known +trouble spot is the mktables script which builds the Unicode support +tables. The default setting of the process data section in Tru64 +should be one gigabyte, but some sites/setups might have lowered that. +The configuration process of Perl checks for too low process limits, +and lowers the optimization for the toke.c if necessary, and also +gives advice on how to raise the process limits +(for example: C<ulimit -d 262144>) Also, Configure might abort with |