First, make sure you have an up-to-date version of Perl. If you
didn't get your Perl source from CPAN, check the latest version at
-L<http://www.cpan.org/src/>. Perl uses a version scheme where even-numbered
+L<https://www.cpan.org/src/>. Perl uses a version scheme where even-numbered
subreleases (like 5.8.x and 5.10.x) are stable maintenance releases and
odd-numbered subreleases (like 5.7.x and 5.9.x) are unstable
development releases. Development releases should not be used in
access to transport layer network proxies. Perl supports only SOCKS
Version 5. The corresponding Configure option is -Dusesocks.
You can find more about SOCKS from wikipedia at
-L<http://en.wikipedia.org/wiki/SOCKS>.
+L<https://en.wikipedia.org/wiki/SOCKS>.
=head3 Dynamic Loading
=item Directories for the perl distribution
-By default, Configure will use the following directories for 5.31.1.
+By default, Configure will use the following directories for 5.31.10.
$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
=item default_inc_excludes_dot
Since version 5.26.0, default perl builds no longer includes C<'.'> as the
-last element of @INC. The old behaviour can restored using
+last element of @INC. The old behaviour can restored using
sh Configure -Udefault_inc_excludes_dot
subdirectory. Porting/Glossary should especially come in handy.
Ports for other systems may also be available. You should check out
-L<http://www.cpan.org/ports> for current information on ports to
+L<https://www.cpan.org/ports> for current information on ports to
various other operating systems.
If you plan to port Perl to a new architecture, study carefully the
Perl can be cross-compiled. It is just not trivial, cross-compilation
rarely is. Perl is routinely cross-compiled for several platforms: as of
-January 2014, these include Android, Blackberry 10, PocketPC aka
-WinCE, ARM Linux, and Solaris. Previous versions of
+June 2019, these include Android, Blackberry 10,
+ARM Linux, and Solaris. Previous versions of
Perl also provided support for Open Zaurus, Symbian, and
the IBM OS/400, but it's unknown if those ports are still functional.
These platforms are known as the B<target> platforms, while the systems
=over 4
-=item WinCE/PocketPC
-
-L<README.ce or perlce|perlce>
-
=item Android
L<"Cross-compilation" in README.android or
=head1 Reporting Problems
-Wherever possible please use the perlbug tool supplied with this Perl
-to report problems, as it automatically includes summary configuration
-information about your perl, which may help us track down problems far
-more quickly. But first you should read the advice in this file,
-carefully re-read the error message and check the relevant manual pages
-on your system, as these may help you find an immediate solution.
-Once you've exhausted the documentation, please report bugs to us using
-the 'perlbug' tool.
-
-The perlbug tool is installed along with perl, so after you have
-completed C<make install> it should be possible to run it with plain
-C<perlbug>. If the install fails, or you want to report problems with
-C<make test> without installing perl, then you can use C<make nok> to
-run perlbug to report the problem, or run it by hand from this source
-directory with C<./perl -Ilib utils/perlbug>
-
-If the build fails too early to run perlbug uninstalled, then please
-B<run> the C<./myconfig> shell script, and mail its output along with
-an accurate description of your problem to perlbug@perl.org
+Please report problems to the GitHub issue tracker at
+https://github.com/Perl/perl5/issues, which will ask for the
+appropriate summary configuration information about your perl, which
+may help us track down problems far more quickly. But first you should
+read the advice in this file, carefully re-read the error message and
+check the relevant manual pages on your system, as these may help you
+find an immediate solution. Once you've exhausted the documentation,
+please report bugs to us using the GitHub tracker.
+
+The summary configuration information can be printed with C<perl -V>.
+If the install fails, or you want to report problems with C<make test>
+without installing perl, then you can run it by hand from this source
+directory with C<./perl -V>.
+
+If the build fails too early to run perl, then please
+B<run> the C<./myconfig> shell script, and include its output along
+with an accurate description of your problem.
If Configure itself fails, and does not generate a config.sh file
-(needed to run C<./myconfig>), then please mail perlbug@perl.org the
+(needed to run C<./myconfig>), then please open an issue with the
description of how Configure fails along with details of your system
--- for example the output from running C<uname -a>
+-- for example the output from running C<uname -a>.
Please try to make your message brief but clear. Brief, clear bug
reports tend to get answered more quickly. Please don't worry if your
necessary. Do not include a complete transcript of your build
session. Just include the failing commands, the relevant error
messages, and whatever preceding commands are necessary to give the
-appropriate context. Plain text should usually be sufficient -- fancy
-attachments or encodings may actually reduce the number of people who
-read your message. Your message will get relayed to over 400
-subscribers around the world so please try to keep it brief but clear.
+appropriate context.
If the bug you are reporting has security implications which make it
-inappropriate to send to a publicly archived mailing list, then see
+inappropriate to send to a public issue tracker, then see
L<perlsec/SECURITY VULNERABILITY CONTACT INFORMATION>
for details of how to report the issue.
If you are unsure what makes a good bug report please read "How to
report Bugs Effectively" by Simon Tatham:
-L<http://www.chiark.greenend.org.uk/~sgtatham/bugs.html>
+L<https://www.chiark.greenend.org.uk/~sgtatham/bugs.html>
=head1 Coexistence with earlier versions of perl 5
-Perl 5.31.1 is not binary compatible with earlier versions of Perl.
+Perl 5.31.10 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. 5.X.Y) to another similar minor version (e.g. 5.X.(Y+1))) without
+In general, you can usually safely upgrade from one stable version of Perl
+(e.g. 5.30.0) to another similar minor version (e.g. 5.30.1) without
re-compiling all of your extensions. You can also safely leave the old
version around in case the new version causes you problems for some
reason.
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.31.1
+ sh Configure -Dprefix=/opt/perl5.31.10
-and adding /opt/perl5.31.1/bin to the shell PATH variable. Such users
+and adding /opt/perl5.31.10/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.28.0 or earlier
+=head2 Upgrading from 5.31.8 or earlier
-B<Perl 5.31.1 may not be binary compatible with Perl 5.28.0 or
+B<Perl 5.31.10 may not be binary compatible with Perl 5.31.8 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.31.1. If you find you do need to rebuild an extension with
-5.31.1, you may safely do so without disturbing the older
+used with 5.31.10. If you find you do need to rebuild an extension with
+5.31.10, 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.31.1 is as follows (under $Config{prefix}):
+in Linux with perl-5.31.10 is as follows (under $Config{prefix}):
./bin/perl
- ./lib/perl5/5.31.1/strict.pm
- ./lib/perl5/5.31.1/warnings.pm
- ./lib/perl5/5.31.1/i686-linux/File/Glob.pm
- ./lib/perl5/5.31.1/feature.pm
- ./lib/perl5/5.31.1/XSLoader.pm
- ./lib/perl5/5.31.1/i686-linux/auto/File/Glob/Glob.so
+ ./lib/perl5/5.31.10/strict.pm
+ ./lib/perl5/5.31.10/warnings.pm
+ ./lib/perl5/5.31.10/i686-linux/File/Glob.pm
+ ./lib/perl5/5.31.10/feature.pm
+ ./lib/perl5/5.31.10/XSLoader.pm
+ ./lib/perl5/5.31.10/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
https://perl5.git.perl.org / perl5.git / blobdiff