new perldelta

[perl5.git] / README.tru64

diff --git a/README.tru64 b/README.tru64
index d171460..c5162b3 100644 (file)
--- a/README.tru64
+++ b/README.tru64
@@ -1,3 +1,5 @@
+# vim: syntax=pod
+

 If you read this file _as_is_, just ignore the funny characters you see.
 It is written in the POD format (see pod/perlpod.pod) which is specially
 designed to be readable as is.
 If you read this file _as_is_, just ignore the funny characters you see.
 It is written in the POD format (see pod/perlpod.pod) which is specially
 designed to be readable as is.


@@ -26,18 +28,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).
 
 (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
 
 
 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
 
 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 +125,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
 
 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
 
 
 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
 
 The exact line numbers may vary between Perl releases.  The warnings
 are benign and can be ignored: in later C compiler releases the warnings