MPE/iX update from Mark Bixby.

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

diff --git a/pod/perldelta.pod b/pod/perldelta.pod
index b3b79b3..b68da5f 100644 (file)
--- a/pod/perldelta.pod
+++ b/pod/perldelta.pod
@@ -624,14 +624,14 @@ included since its further use is discouraged.
 
 =item *
 
-C<Encode>, by Nick Ing-Simmons, provides a mechanism to translate
-between different character encodings.  Support for Unicode,
-ISO-8859-*, ASCII, CP*, KOI8-R, and three variants of EBCDIC are
-compiled in to the module.  Several other encodings (like Chinese,
-Japanese, Korean, and MacIntosh encodings) are included and will be
-loaded at runtime.  (For space considerations, the largest Chinese
-encodings have been separated into their own CPAN module,
-Encode::HanExtra).  See L<Encode>.
+C<Encode>, by Nick Ing-Simmons and Dan Kogai, provides a mechanism to
+translate between different character encodings.  Support for Unicode,
+ISO-8859-1, and ASCII are compiled in to the module.  Several other
+encodings (like the rest of the ISO-8859, CP*/Win*, Mac, KOI8-R, three
+variants EBCDIC, Chinese, Japanese, and Korean encodings) are included
+and can be loaded at runtime.  (For space considerations, the largest
+Chinese encodings have been separated into their own CPAN module,
+Encode::HanExtra, which Encode will use if available).  See L<Encode>.
 
 Any encoding supported by Encode module is also available to the
 ":encoding()" layer if PerlIO is used.
@@ -2592,6 +2592,15 @@ are run by hand, they succeed.  We suggest upgrading to at least
 vac version 5.0.1.0, that has been known to compile Perl correctly.
 "lslpp -L|grep vac.C" will tell you the vac version. See README.aix.
 
+=item *
+
+If building threaded Perl, you may get compilation warning from pp_sys.c:
+
+  "pp_sys.c", line 4651.39: 1506-280 (W) Function argument assignment between types "unsigned char*" and "const void*" is not allowed.
+
+This is harmless; it is caused by the getnetbyaddr() and getnetbyaddr_r()
+having slightly different types for their first argument.
+
 =back
 
 =head2 Amiga Perl Invoking Mystery
@@ -2600,19 +2609,20 @@ One cannot call Perl using the C<volume:> syntax, that is, C<perl -v>
 works, but for example C<bin:perl -v> doesn't.  The exact reason isn't
 known but the current suspect is the F<ixemul> library.
 
-=head2 mod_perl 1.3 Doesn't Build With -D_GNU_SOURCE
+=head2 mod_perl 1.26 Doesn't Build With -D_GNU_SOURCE
 
 In Linux, building mod_perl with B<threaded> Perl 5.8.0 does not work
 because starting from 5.8.0 building a threaded Perl uses the
--D_GNU_SOURCE flag.  The Apache 1.3 sources that are built alongside
-the mod_perl don't like that flag and the compilation dies because of
-function prototype conflicts.  This may or may not get fixed in later
-releases of mod_perl 1.3 or Apache 1.3 (fixing the problem in Perl is
-less likely since threaded Perl now needs the -D_GNU_SOURCE>).
-Workarounds include using non-threaded Perl and using Apache 2.0.
+-D_GNU_SOURCE flag.  The Apache 1.3.23 sources that are built
+alongside mod_perl don't like that flag and the compilation dies
+because of function prototype conflicts.  This may or may not get
+fixed in later releases of mod_perl than the current 1.26 or in later
+releases of Apache than the current 1.3.23 (fixing the problem in Perl
+is less likely since threaded Perl in Linux now needs the -D_GNU_SOURCE>).
+Workarounds include using non-threaded Perl and using Apache 2.0. 
 An obvious workaround would be to stop the -D_GNU_SOURCE from reaching
-the Apache 1.3 sources, but as of Perl 5.8.0, the complex build system
-of mod_perl has foiled this idea.
+the Apache 1.3.23 sources, but as of Perl 5.8.0, the complex build
+system of mod_perl has foiled this idea.
 
 =head2 lib/ftmp-security tests warn 'system possibly insecure'