X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=blobdiff_plain;f=README.tru64;h=b2509b86c72eb7bc02313984a7f02eeac8dbe68f;hb=0b8d6043dc77b60f4e7020acd7548c8bcae74009;hp=d65175a4c0b883a554ad5c9f4b0f37eb8bac75a3;hpb=d780cd7a0195e946e636d3ee546f6ef4f21d6acc;p=p5sagit%2Fp5-mst-13.2.git

diff --git a/README.tru64 b/README.tru64
index d65175a..b2509b8 100644
--- a/README.tru64
+++ b/README.tru64
@@ -48,6 +48,14 @@ You cannot Configure Perl to use long doubles unless you have at least
 Tru64 V5.0, the long double support simply wasn't functional before
 that.
 
+At the time of this writing, there's a bug in the Tru64 libc printing
+of long doubles when not using "e" notation.  The values are correct
+and usable, but you only get a limited number of digits displayed
+unless you force the issue by using C<printf "%.33e",$num> or the like.
+For Tru64 versions V5.0A through V5.1A, a patch is expected sometime after
+perl 5.8.0 is released.  If your libc has not yet been patched, you'll get
+a warning from Configure when selecting long doubles.
+
 =head2 64-bit Perl on Tru64
 
 In Tru64 Perl's integers are automatically 64-bit wide, there is
@@ -63,7 +71,9 @@ release) see two warnings like this
         return HUGE_VAL;
     -----------^
 
-    cc: Warning: POSIX.xs, line 1304: In this statement, floating-point overflow occurs in evaluating the expression "1.8e308". (floatoverfl)
+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;
     -------------------^
 
@@ -83,6 +93,14 @@ During "make test" the C<comp/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.
 
+=head1 ext/ODBM_File/odbm Test Failing With Static Builds
+
+The ext/ODBM_File/odbm is known to fail with static builds
+(Configure -Dusedl) due to a known bug in Tru64's static libdbm
+library.  The good news is that you very probably don't need to ever
+use the ODBM_File extension since more advanced NDBM_File works fine,
+not to mention the even more advanced DB_File.
+
 =head1 AUTHOR
 
 Jarkko Hietaniemi <jhi@iki.fi>