X-Git-Url: https://perl5.git.perl.org/perl5.git/blobdiff_plain/1874162f037456b666aa88174a3a68546de0c4de..ed65a01d6f36d0b6673202d6a2e873126e80c971:/README.tru64

diff --git a/README.tru64 b/README.tru64
index 5e3ae85..7b596a9 100644
--- a/README.tru64
+++ b/README.tru64
@@ -26,18 +26,21 @@ 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
 
-    Build a threading Perl? [n]
-    Configure[2437]: Syntax error at line 1 : 'config.sh' is not expected.
+ Build a threading Perl? [n]
+ Configure[2437]: Syntax error at line 1 : 'config.sh' is not expected.
 
 This indicates that Configure is being run with a broken Korn shell
 (even though you think you are using a Bourne shell by using
@@ -120,17 +123,17 @@ since pointers are automatically 64-bit wide.
 When compiling Perl in Tru64 you may (depending on the compiler
 release) see two warnings like this
 
-    cc: Warning: numeric.c, line 104: In this statement, floating-point
-    overflow occurs in evaluating the expression "1.8e308". (floatoverfl)
-        return HUGE_VAL;
-    -----------^
+ cc: Warning: numeric.c, line 104: In this statement, floating-point
+ overflow occurs in evaluating the expression "1.8e308". (floatoverfl)
+     return HUGE_VAL;
+ -----------^
 
 and when compiling the POSIX extension
 
-    cc: Warning: const-c.inc, line 2007: In this statement, floating-point
-    overflow occurs in evaluating the expression "1.8e308". (floatoverfl)
-                return HUGE_VAL;
-    -------------------^
+ cc: Warning: const-c.inc, line 2007: In this statement, floating-point
+ overflow occurs in evaluating the expression "1.8e308". (floatoverfl)
+             return HUGE_VAL;
+ -------------------^
 
 The exact line numbers may vary between Perl releases.  The warnings
 are benign and can be ignored: in later C compiler releases the warnings
@@ -145,7 +148,7 @@ instructs Perl not to use the feature.
 
 =head1 Testing Perl on Tru64
 
-During "make test" the C<comp/cpp> will be skipped because on Tru64 it
+During "make test" the C<comp>/C<cpp> will be skipped because on Tru64 it
 cannot be tested before Perl has been installed.  The test refers to
 the use of the C<-P> option of Perl.