(that is, Perl's numbers). Use Configure -Duselongdouble to enable
this support (if it is available).
+Note that the exact format and range of long doubles varies:
+the most common is the x86 80-bit (64 bits of mantissa) format,
+but there are others, with different mantissa and exponent ranges.
+
=head3 "more bits"
You can "Configure -Dusemorebits" to turn on both the 64-bit support
To build a shared libperl, the environment variable controlling shared
library search (LD_LIBRARY_PATH in most systems, DYLD_LIBRARY_PATH for
-NeXTSTEP/OPENSTEP/Darwin, LD_LIBRARY_PATH/SHLIB_PATH
+Darwin, LD_LIBRARY_PATH/SHLIB_PATH
for HP-UX, LIBPATH for AIX, PATH for Cygwin) must be set up to include
the Perl build directory because that's where the shared libperl will
be created. Configure arranges makefile to have the correct shared
=item Directories for the perl distribution
-By default, Configure will use the following directories for 5.19.10.
+By default, Configure will use the following directories for 5.21.4.
$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
if your cc -E can't read from stdin.
c2ph, pstruct Scripts for handling C structures in header
files.
- config_data Manage Module::Build-like module configuration.
corelist Shows versions of modules that come with
different
versions of perl.
=head1 Coexistence with earlier versions of perl 5
-Perl 5.19.10 is not binary compatible with earlier versions of Perl.
+Perl 5.21.4 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.19.10
+ sh Configure -Dprefix=/opt/perl5.21.4
-and adding /opt/perl5.19.10/bin to the shell PATH variable. Such users
+and adding /opt/perl5.21.4/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.19.0 or earlier
+=head2 Upgrading from 5.21.3 or earlier
-B<Perl 5.19.10 may not be binary compatible with Perl 5.19.7 or
+B<Perl 5.21.4 may not be binary compatible with Perl 5.21.3 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.19.10. If you find you do need to rebuild an extension with
-5.19.10, you may safely do so without disturbing the older
+used with 5.21.4. If you find you do need to rebuild an extension with
+5.21.4, 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.19.10 is as follows (under $Config{prefix}):
+in Linux with perl-5.21.4 is as follows (under $Config{prefix}):
./bin/perl
- ./lib/perl5/5.19.10/strict.pm
- ./lib/perl5/5.19.10/warnings.pm
- ./lib/perl5/5.19.10/i686-linux/File/Glob.pm
- ./lib/perl5/5.19.10/feature.pm
- ./lib/perl5/5.19.10/XSLoader.pm
- ./lib/perl5/5.19.10/i686-linux/auto/File/Glob/Glob.so
+ ./lib/perl5/5.21.4/strict.pm
+ ./lib/perl5/5.21.4/warnings.pm
+ ./lib/perl5/5.21.4/i686-linux/File/Glob.pm
+ ./lib/perl5/5.21.4/feature.pm
+ ./lib/perl5/5.21.4/XSLoader.pm
+ ./lib/perl5/5.21.4/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.