=item Directories for the perl distribution
-By default, Configure will use the following directories for 5.24.0.
+By default, Configure will use the following directories for 5.25.2.
$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
Additionally, a cross-compilation toolchain will usually install it's own
logical system root somewhere -- that is, it'll create a directory
-somewhere which includes subdirectories like 'include' or 'lib'. For
-example, you may end up with C</skiff/local/arm-linux>, where
-C</skiff/local/arm-linux/bin> holds the binaries for cross-compilation,
-C</skiff/local/arm-linux/include> has the headers, and
-C</skiff/local/arm-linux/lib> has the library files.
+somewhere which includes subdirectories like C<'include'> or C<'lib'>. For
+example, you may end up with F</skiff/local/arm-linux>, where
+F</skiff/local/arm-linux/bin> holds the binaries for cross-compilation,
+F</skiff/local/arm-linux/include> has the headers, and
+F</skiff/local/arm-linux/lib> has the library files.
If this is the case, and you are using a compiler that understands
C<--sysroot>, like gcc or clang, you'll want to specify the
C<-Dsysroot> option for Configure:
=head1 Coexistence with earlier versions of perl 5
-Perl 5.24.0 is not binary compatible with earlier versions of Perl.
+Perl 5.25.2 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
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.24.0
+ sh Configure -Dprefix=/opt/perl5.25.2
-and adding /opt/perl5.24.0/bin to the shell PATH variable. Such users
+and adding /opt/perl5.25.2/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 v5.22 or earlier
+=head2 Upgrading from v5.25.0 or earlier
-B<Perl 5.24.0 may not be binary compatible with Perl v5.22 or
+B<Perl 5.25.2 may not be binary compatible with Perl v5.22 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.24.0. If you find you do need to rebuild an extension with
-5.24.0, you may safely do so without disturbing the older
+used with 5.25.2. If you find you do need to rebuild an extension with
+5.25.2, 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.24.0 is as follows (under $Config{prefix}):
+in Linux with perl-5.25.2 is as follows (under $Config{prefix}):
./bin/perl
- ./lib/perl5/5.24.0/strict.pm
- ./lib/perl5/5.24.0/warnings.pm
- ./lib/perl5/5.24.0/i686-linux/File/Glob.pm
- ./lib/perl5/5.24.0/feature.pm
- ./lib/perl5/5.24.0/XSLoader.pm
- ./lib/perl5/5.24.0/i686-linux/auto/File/Glob/Glob.so
+ ./lib/perl5/5.25.2/strict.pm
+ ./lib/perl5/5.25.2/warnings.pm
+ ./lib/perl5/5.25.2/i686-linux/File/Glob.pm
+ ./lib/perl5/5.25.2/feature.pm
+ ./lib/perl5/5.25.2/XSLoader.pm
+ ./lib/perl5/5.25.2/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