Provice virtual $Config{ccflags_nolargefiles} etc.

[p5sagit/p5-mst-13.2.git] / pod / perldelta.pod

diff --git a/pod/perldelta.pod b/pod/perldelta.pod
index ad438e7..d0c8113 100644 (file)
--- a/pod/perldelta.pod
+++ b/pod/perldelta.pod
@@ -155,8 +155,9 @@ the podlators bundle, Pod::LaTeX, Pod::Parser, Term::ANSIColor, Test.
 =item *
 
 Bug fixes and minor enhancements have been applied to B::Deparse,
-Data::Dumper, IO::Poll, IO::Socket::INET, Math::BigFloat, Math::Complex,
-re, SelfLoader, Sys::SysLog, Test::Harness, Text::Wrap, UNIVERSAL.
+Data::Dumper, IO::Poll, IO::Socket::INET, Math::BigFloat,
+Math::Complex, Math::Trig, re, SelfLoader, Sys::SysLog, Test::Harness,
+Text::Wrap, UNIVERSAL.
 
 =item *
 
@@ -217,12 +218,6 @@ The Emacs perl mode (emacs/cperl-mode.el) has been updated to version 4.31.
 
 =item *
 
-The long-dormant perl bytecompiler has been added to the list of
-installed utilities since the bytecompiler backend has been improved.
-The bytecompiler is still very much experimental, though.
-
-=item *
-
 Perlbug is now much more robust.  It also sends the bug report to perl.org,
 not perl.com.
 
@@ -743,12 +738,17 @@ The plan is to bring them back.
 
 Certain extensions like mod_perl and BSD::Resource are known to have
 issues with `largefiles', a change brought by Perl 5.6.0 in which file
-offsets default to 64 bits wide where supported.  Modules may fail to
+offsets default to 64 bits wide, where supported.  Modules may fail to
 compile at all or compile and work incorrectly.  Currently there is no
-good solution for the problem, but Configure now stores the relevant
-flags and libraries in the %Config hash so the extensions that are having
-problems can try configuring themselves without the largefileness.
-This is admittedly not a clean solution.
+good solution for the problem, but Configure now provides appropriate
+non-largefile ccflags, ldflags, libswanted, and libs in the %Config
+hash (e.g., $Config{ccflags_nolargefiles}) so the extensions that are
+having problems can try configuring themselves without the
+largefileness.  This is admittedly not a clean solution, and the
+solution may not even work at all.  One potential failure is whether
+one can (or, if one can, whether it's a good idea) link together at
+all binaries with different ideas about file offsets, all this is
+platform-dependent.
 
 =over 4