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.
-In fact, the type may not be called "long double" at C level, and
-therefore the C<uselongdouble> means "using floating point larger
-than double".
=head3 "more bits"
=item Directories for the perl distribution
-By default, Configure will use the following directories for 5.23.1.
+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
=item Bad arg length for semctl, is XX, should be ZZZ
-If you get this error message from the ext/IPC/SysV/t/sem test, your
+If you get this error message from the F<cpan/IPC-SysV/t/sem.t> test, your
System V IPC may be broken. The XX typically is 20, and that is what ZZZ
also should be. Consider upgrading your OS, or reconfiguring your OS
to include the System V semaphores.
-=item ext/IPC/SysV/t/sem........semget: No space left on device
+=item cpan/IPC-SysV/t/sem........semget: No space left on device
Either your account or the whole system has run out of semaphores. Or
both. Either list the semaphores with "ipcs" and remove the unneeded
UTS may need one or more of -K or -g, and #undef LSTAT.
-FreeBSD can fail the ext/IPC/SysV/t/sem.t test if SysV IPC has not been
+FreeBSD can fail the F<cpan/IPC-SysV/t/sem.t> test if SysV IPC has not been
configured in the kernel. Perl tries to detect this, though, and
you will get a message telling you what to do.
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:
these tests might fail. If possible, try running the tests again
with the system under a lighter load. These timing-sensitive
and load-sensitive tests include F<t/op/alarm.t>,
-F<ext/Time-HiRes/t/HiRes.t>, F<ext/threads-shared/t/waithires.t>,
-F<ext/threads-shared/t/stress.t>, F<lib/Benchmark.t>,
+F<dist/Time-HiRes/t/alarm.t>, F<dist/Time-HiRes/t/clock.t>,
+F<dist/Time-HiRes/t/itimer.t>, F<dist/Time-HiRes/t/usleep.t>,
+F<dist/threads-shared/t/waithires.t>,
+F<dist/threads-shared/t/stress.t>, F<lib/Benchmark.t>,
F<lib/Memoize/t/expmod_t.t>, and F<lib/Memoize/t/speed.t>.
You might also experience some failures in F<t/op/stat.t> if you build
read your message. Your message will get relayed to over 400
subscribers around the world so please try to keep it brief but clear.
-If the bug you are reporting has security implications, which make it
-inappropriate to send to a publicly archived mailing list, then please
-send it to perl5-security-report@perl.org. This points to a closed
-subscription unarchived mailing list, which includes all the core
-committers, who be able to help assess the impact of issues, figure out
-a resolution, and help co-ordinate the release of patches to mitigate or
-fix the problem across all platforms on which Perl is supported. Please
-only use this address for security issues in the Perl core, not for
-modules independently distributed on CPAN.
+If the bug you are reporting has security implications which make it
+inappropriate to send to a publicly archived mailing list, 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:
=head1 Coexistence with earlier versions of perl 5
-Perl 5.23.1 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.23.1
+ sh Configure -Dprefix=/opt/perl5.25.2
-and adding /opt/perl5.23.1/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 5.23.0 or earlier
+=head2 Upgrading from v5.25.0 or earlier
-B<Perl 5.23.1 may not be binary compatible with Perl 5.23.0 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.23.1. If you find you do need to rebuild an extension with
-5.23.1, 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.23.1 is as follows (under $Config{prefix}):
+in Linux with perl-5.25.2 is as follows (under $Config{prefix}):
./bin/perl
- ./lib/perl5/5.23.1/strict.pm
- ./lib/perl5/5.23.1/warnings.pm
- ./lib/perl5/5.23.1/i686-linux/File/Glob.pm
- ./lib/perl5/5.23.1/feature.pm
- ./lib/perl5/5.23.1/XSLoader.pm
- ./lib/perl5/5.23.1/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