in the Perl language in the current release. Please see
pod/perldelta.pod for a description of what's changed. See your
installed copy of the perllocal.pod file for a (possibly incomplete)
-list of locally installed modules. Also see CPAN::autobundle for one
-way to make a "bundle" of your currently installed modules.
+list of locally installed modules. Also see the L<CPAN> module's
+C<autobundle> function for one way to make a "bundle" of your currently
+installed modules.
=head1 Run Configure
=item Directories for the perl distribution
-By default, Configure will use the following directories for 5.17.0.
+By default, Configure will use the following directories for 5.17.6.
$version is the full perl version number, including subversion, e.g.
5.12.3, and $archname is a string like sun4-sunos,
determined by Configure. The full definitions of all Configure
directory, and has to include architecture-dependent directories separately,
eg.
- sh Configure -Dinc_version_list="5.17.0/x86_64-linux 5.14.0" ...
+ sh Configure -Dinc_version_list="5.16.0/x86_64-linux 5.16.0" ...
When using the newer perl, you can add these paths again in the
PERL5LIB environment variable or with perl's -I runtime option.
If you have any additional changes to make to the C compiler command
line, they can be made in cflags.SH. For instance, to turn off the
-optimizer on toke.c, find the line in the switch structure for
-toke.c and put the command optimize='-g' before the ;; . You
-should not edit the generated file cflags directly, as your changes will
+optimizer on toke.c, find the switch structure marked 'or customize here',
+and add a line for toke.c ahead of the catch-all *) so that it now reads:
+
+ : or customize here
+
+ case "$file" in
+ toke) optimize='-g' ;;
+ *) ;;
+
+You should not edit the generated file cflags directly, as your changes will
be lost the next time you run Configure, or if you edit config.sh.
To explore various ways of changing ccflags from within a hint file,
Perl can be cross-compiled. It is just not trivial, cross-compilation
rarely is. Perl is routinely cross-compiled for many platforms (as of
-June 2005 at least PocketPC aka WinCE, Open Zaurus, EPOC, Symbian, and
+June 2005 at least PocketPC aka WinCE, Open Zaurus, Symbian, and
the IBM OS/400). These platforms are known as the B<target> platforms,
while the systems where the compilation takes place are the B<host>
platforms.
Cross/README
-=item EPOC
-
-README.epoc
-
=item Symbian
README.symbian
=head1 Coexistence with earlier versions of perl 5
-Perl 5.17 is not binary compatible with earlier versions of Perl.
+Perl 5.17.6 is not binary compatible with earlier versions of Perl.
In other words, you will have to recompile your XS modules.
In general, you can usually safely upgrade from one version of Perl (e.g.
libraries after 5.6.0, but not for executables. TODO?) One convenient
way to do this is by using a separate prefix for each version, such as
- sh Configure -Dprefix=/opt/perl5.17.0
+ sh Configure -Dprefix=/opt/perl5.17.6
-and adding /opt/perl5.17.0/bin to the shell PATH variable. Such users
+and adding /opt/perl5.17.6/bin to the shell PATH variable. Such users
may also wish to add a symbolic link /usr/local/bin/perl so that
scripts can still start with #!/usr/local/bin/perl.
subversions may not have all the compatibility wrinkles ironed out
yet.
-=head2 Upgrading from 5.16.0 or earlier
+=head2 Upgrading from 5.17.5 or earlier
-B<Perl 5.17.0 may not be is binary incompatible with Perl 5.16.0 or
-earlier Perl release.> Perl modules having binary parts
+B<Perl 5.17.6 may not be binary compatible with Perl 5.17.5 or
+earlier Perl releases.> Perl modules having binary parts
(meaning that a C compiler is used) will have to be recompiled to be
-used with 5.17.0. If you find you do need to rebuild an extension with
-5.17.0, you may safely do so without disturbing the older
+used with 5.17.6. If you find you do need to rebuild an extension with
+5.17.6, you may safely do so without disturbing the older
installations. (See L<"Coexistence with earlier versions of perl 5">
above.)
print("$f\n");
}
-in Linux with perl-5.17.0 is as follows (under $Config{prefix}):
+in Linux with perl-5.17.6 is as follows (under $Config{prefix}):
./bin/perl
- ./lib/perl5/5.17.0/strict.pm
- ./lib/perl5/5.17.0/warnings.pm
- ./lib/perl5/5.17.0/i686-linux/File/Glob.pm
- ./lib/perl5/5.17.0/feature.pm
- ./lib/perl5/5.17.0/XSLoader.pm
- ./lib/perl5/5.17.0/i686-linux/auto/File/Glob/Glob.so
+ ./lib/perl5/5.17.6/strict.pm
+ ./lib/perl5/5.17.6/warnings.pm
+ ./lib/perl5/5.17.6/i686-linux/File/Glob.pm
+ ./lib/perl5/5.17.6/feature.pm
+ ./lib/perl5/5.17.6/XSLoader.pm
+ ./lib/perl5/5.17.6/i686-linux/auto/File/Glob/Glob.so
Secondly, for perl-5.10.1, the Debian perl-base package contains 591 files,
(of which 510 are for lib/unicore) totaling about 3.5MB in its i386 version.
https://perl5.git.perl.org / perl5.git / blobdiff