perldelta for 56f81afc0f, which is actually in 5.21.8

[perl5.git] / README.tru64

diff --git a/README.tru64 b/README.tru64
index 109cf5d..5e3ae85 100644 (file)
--- a/README.tru64
+++ b/README.tru64
@@ -37,7 +37,7 @@ necessary, and also gives advice on how to raise the process limits.
 Also, Configure might abort with
 
     Build a threading Perl? [n]
-    Configure[2437]: Syntax error at line 1 : `config.sh' is not expected.
+    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,13 +120,15 @@ 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)
+    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)
+    cc: Warning: const-c.inc, line 2007: In this statement, floating-point
+    overflow occurs in evaluating the expression "1.8e308". (floatoverfl)
                 return HUGE_VAL;
     -------------------^
 
@@ -165,6 +167,19 @@ you need to either recompile your Perl in Tru64 4.0D or upgrade your
 Tru64 4.0D to at least 4.0F: the sockatmark() system call was
 added in Tru64 4.0F, and the IO extension refers that symbol.
 
+=head1 read_cur_obj_info: bad file magic number
+
+You may be mixing the Tru64 cc/ar/ld with the GNU gcc/ar/ld.
+That may work, but sometimes it doesn't (your gcc or GNU utils
+may have been compiled for an incompatible OS release).
+
+Try 'which ld' and 'which ld' (or try 'ar --version' and 'ld --version',
+which work only for the GNU tools, and will announce themselves to be such),
+and adjust your PATH so that you are consistently using either
+the native tools or the GNU tools.  After fixing your PATH, you should
+do 'make distclean' and start all the way from running the Configure
+since you may have quite a confused situation.
+
 =head1 AUTHOR
 
 Jarkko Hietaniemi <jhi@iki.fi>