Re: [ID 20020416.001] 'close' does not report failure when buffer flush fails

[p5sagit/p5-mst-13.2.git] / README.tru64

diff --git a/README.tru64 b/README.tru64
index ce2181a..b2509b8 100644 (file)
--- a/README.tru64
+++ b/README.tru64
@@ -71,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;
     -------------------^
 
@@ -91,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>