| 1 |
.\" -*- mode: troff; coding: utf-8 -*- |
| 2 |
.\" Automatically generated by Pod::Man 5.0102 (Pod::Simple 3.45) |
| 3 |
.\" |
| 4 |
.\" Standard preamble: |
| 5 |
.\" ======================================================================== |
| 6 |
.de Sp \" Vertical space (when we can't use .PP) |
| 7 |
.if t .sp .5v |
| 8 |
.if n .sp |
| 9 |
.. |
| 10 |
.de Vb \" Begin verbatim text |
| 11 |
.ft CW |
| 12 |
.nf |
| 13 |
.ne \\$1 |
| 14 |
.. |
| 15 |
.de Ve \" End verbatim text |
| 16 |
.ft R |
| 17 |
.fi |
| 18 |
.. |
| 19 |
.\" \*(C` and \*(C' are quotes in nroff, nothing in troff, for use with C<>. |
| 20 |
.ie n \{\ |
| 21 |
. ds C` "" |
| 22 |
. ds C' "" |
| 23 |
'br\} |
| 24 |
.el\{\ |
| 25 |
. ds C` |
| 26 |
. ds C' |
| 27 |
'br\} |
| 28 |
.\" |
| 29 |
.\" Escape single quotes in literal strings from groff's Unicode transform. |
| 30 |
.ie \n(.g .ds Aq \(aq |
| 31 |
.el .ds Aq ' |
| 32 |
.\" |
| 33 |
.\" If the F register is >0, we'll generate index entries on stderr for |
| 34 |
.\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index |
| 35 |
.\" entries marked with X<> in POD. Of course, you'll have to process the |
| 36 |
.\" output yourself in some meaningful fashion. |
| 37 |
.\" |
| 38 |
.\" Avoid warning from groff about undefined register 'F'. |
| 39 |
.de IX |
| 40 |
.. |
| 41 |
.nr rF 0 |
| 42 |
.if \n(.g .if rF .nr rF 1 |
| 43 |
.if (\n(rF:(\n(.g==0)) \{\ |
| 44 |
. if \nF \{\ |
| 45 |
. de IX |
| 46 |
. tm Index:\\$1\t\\n%\t"\\$2" |
| 47 |
.. |
| 48 |
. if !\nF==2 \{\ |
| 49 |
. nr % 0 |
| 50 |
. nr F 2 |
| 51 |
. \} |
| 52 |
. \} |
| 53 |
.\} |
| 54 |
.rr rF |
| 55 |
.\" ======================================================================== |
| 56 |
.\" |
| 57 |
.IX Title "PERLSOLARIS 1" |
| 58 |
.TH PERLSOLARIS 1 2025-11-16 "perl v5.40.1" "Perl Programmers Reference Guide" |
| 59 |
.\" For nroff, turn off justification. Always turn off hyphenation; it makes |
| 60 |
.\" way too many mistakes in technical documents. |
| 61 |
.if n .ad l |
| 62 |
.nh |
| 63 |
.SH NAME |
| 64 |
perlsolaris \- Perl version 5 on Solaris systems |
| 65 |
.SH DESCRIPTION |
| 66 |
.IX Header "DESCRIPTION" |
| 67 |
This document describes various features of Sun's Solaris operating system |
| 68 |
that will affect how Perl version 5 (hereafter just perl) is |
| 69 |
compiled and/or runs. Some issues relating to the older SunOS 4.x are |
| 70 |
also discussed, though they may be out of date. |
| 71 |
.PP |
| 72 |
For the most part, everything should just work. |
| 73 |
.PP |
| 74 |
Starting with Solaris 8, perl5.00503 (or higher) is supplied with the |
| 75 |
operating system, so you might not even need to build a newer version |
| 76 |
of perl at all. The Sun-supplied version is installed in /usr/perl5 |
| 77 |
with \fI/usr/bin/perl\fR pointing to \fI/usr/perl5/bin/perl\fR. Do not disturb |
| 78 |
that installation unless you really know what you are doing. If you |
| 79 |
remove the perl supplied with the OS, you will render some bits of |
| 80 |
your system inoperable. If you wish to install a newer version of perl, |
| 81 |
install it under a different prefix from /usr/perl5. Common prefixes |
| 82 |
to use are /usr/local and /opt/perl. |
| 83 |
.PP |
| 84 |
You may wish to put your version of perl in the PATH of all users by |
| 85 |
changing the link \fI/usr/bin/perl\fR. This is probably OK, as most perl |
| 86 |
scripts shipped with Solaris use an explicit path. (There are a few |
| 87 |
exceptions, such as \fI/usr/bin/rpm2cpio\fR and \fI/etc/rcm/scripts/README\fR, but |
| 88 |
these are also sufficiently generic that the actual version of perl |
| 89 |
probably doesn't matter too much.) |
| 90 |
.PP |
| 91 |
Solaris ships with a range of Solaris-specific modules. If you choose |
| 92 |
to install your own version of perl you will find the source of many of |
| 93 |
these modules is available on CPAN under the Sun::Solaris:: namespace. |
| 94 |
.PP |
| 95 |
Solaris may include two versions of perl, e.g. Solaris 9 includes |
| 96 |
both 5.005_03 and 5.6.1. This is to provide stability across Solaris |
| 97 |
releases, in cases where a later perl version has incompatibilities |
| 98 |
with the version included in the preceding Solaris release. The |
| 99 |
default perl version will always be the most recent, and in general |
| 100 |
the old version will only be retained for one Solaris release. Note |
| 101 |
also that the default perl will NOT be configured to search for modules |
| 102 |
in the older version, again due to compatibility/stability concerns. |
| 103 |
As a consequence if you upgrade Solaris, you will have to |
| 104 |
rebuild/reinstall any additional CPAN modules that you installed for |
| 105 |
the previous Solaris version. See the CPAN manpage under 'autobundle' |
| 106 |
for a quick way of doing this. |
| 107 |
.PP |
| 108 |
As an interim measure, you may either change the #! line of your |
| 109 |
scripts to specifically refer to the old perl version, e.g. on |
| 110 |
Solaris 9 use #!/usr/perl5/5.00503/bin/perl to use the perl version |
| 111 |
that was the default for Solaris 8, or if you have a large number of |
| 112 |
scripts it may be more convenient to make the old version of perl the |
| 113 |
default on your system. You can do this by changing the appropriate |
| 114 |
symlinks under /usr/perl5 as follows (example for Solaris 9): |
| 115 |
.PP |
| 116 |
.Vb 7 |
| 117 |
\& # cd /usr/perl5 |
| 118 |
\& # rm bin man pod |
| 119 |
\& # ln \-s ./5.00503/bin |
| 120 |
\& # ln \-s ./5.00503/man |
| 121 |
\& # ln \-s ./5.00503/lib/pod |
| 122 |
\& # rm /usr/bin/perl |
| 123 |
\& # ln \-s ../perl5/5.00503/bin/perl /usr/bin/perl |
| 124 |
.Ve |
| 125 |
.PP |
| 126 |
In both cases this should only be considered to be a temporary |
| 127 |
measure \- you should upgrade to the later version of perl as soon as |
| 128 |
is practicable. |
| 129 |
.PP |
| 130 |
Note also that the perl command-line utilities (e.g. perldoc) and any |
| 131 |
that are added by modules that you install will be under |
| 132 |
/usr/perl5/bin, so that directory should be added to your PATH. |
| 133 |
.SS "Solaris Version Numbers" |
| 134 |
.IX Subsection "Solaris Version Numbers" |
| 135 |
For consistency with common usage, perl's Configure script performs |
| 136 |
some minor manipulations on the operating system name and version |
| 137 |
number as reported by uname. Here's a partial translation table: |
| 138 |
.PP |
| 139 |
.Vb 7 |
| 140 |
\& Sun: perl\*(Aqs Configure: |
| 141 |
\& uname uname \-r Name osname osvers |
| 142 |
\& SunOS 4.1.3 Solaris 1.1 sunos 4.1.3 |
| 143 |
\& SunOS 5.6 Solaris 2.6 solaris 2.6 |
| 144 |
\& SunOS 5.8 Solaris 8 solaris 2.8 |
| 145 |
\& SunOS 5.9 Solaris 9 solaris 2.9 |
| 146 |
\& SunOS 5.10 Solaris 10 solaris 2.10 |
| 147 |
.Ve |
| 148 |
.PP |
| 149 |
The complete table can be found in the Sun Managers' FAQ |
| 150 |
<ftp://ftp.cs.toronto.edu/pub/jdd/sunmanagers/faq> under |
| 151 |
"9.1) Which Sun models run which versions of SunOS?". |
| 152 |
.SH RESOURCES |
| 153 |
.IX Header "RESOURCES" |
| 154 |
There are many, many sources for Solaris information. A few of the |
| 155 |
important ones for perl: |
| 156 |
.IP "Solaris FAQ" 4 |
| 157 |
.IX Item "Solaris FAQ" |
| 158 |
The Solaris FAQ is available at |
| 159 |
<http://www.science.uva.nl/pub/solaris/solaris2.html>. |
| 160 |
.Sp |
| 161 |
The Sun Managers' FAQ is available at |
| 162 |
<ftp://ftp.cs.toronto.edu/pub/jdd/sunmanagers/faq> |
| 163 |
.IP "Precompiled Binaries" 4 |
| 164 |
.IX Item "Precompiled Binaries" |
| 165 |
Precompiled binaries, links to many sites, and much, much more are |
| 166 |
available at <http://www.sunfreeware.com/> and |
| 167 |
<http://www.blastwave.org/>. |
| 168 |
.IP "Solaris Documentation" 4 |
| 169 |
.IX Item "Solaris Documentation" |
| 170 |
All Solaris documentation is available on-line at <http://docs.sun.com/>. |
| 171 |
.SH "SETTING UP" |
| 172 |
.IX Header "SETTING UP" |
| 173 |
.SS "File Extraction Problems on Solaris" |
| 174 |
.IX Subsection "File Extraction Problems on Solaris" |
| 175 |
Be sure to use a tar program compiled under Solaris (not SunOS 4.x) |
| 176 |
to extract the perl\-5.x.x.tar.gz file. Do not use GNU tar compiled |
| 177 |
for SunOS4 on Solaris. (GNU tar compiled for Solaris should be fine.) |
| 178 |
When you run SunOS4 binaries on Solaris, the run-time system magically |
| 179 |
alters pathnames matching m#lib/locale# so that when tar tries to create |
| 180 |
lib/locale.pm, a file named lib/oldlocale.pm gets created instead. |
| 181 |
If you found this advice too late and used a SunOS4\-compiled tar |
| 182 |
anyway, you must find the incorrectly renamed file and move it back |
| 183 |
to lib/locale.pm. |
| 184 |
.SS "Compiler and Related Tools on Solaris" |
| 185 |
.IX Subsection "Compiler and Related Tools on Solaris" |
| 186 |
You must use an ANSI C compiler to build perl. Perl can be compiled |
| 187 |
with either Sun's add-on C compiler or with gcc. The C compiler that |
| 188 |
shipped with SunOS4 will not do. |
| 189 |
.PP |
| 190 |
\fIInclude /usr/ccs/bin/ in your PATH\fR |
| 191 |
.IX Subsection "Include /usr/ccs/bin/ in your PATH" |
| 192 |
.PP |
| 193 |
Several tools needed to build perl are located in /usr/ccs/bin/: ar, |
| 194 |
as, ld, and make. Make sure that /usr/ccs/bin/ is in your PATH. |
| 195 |
.PP |
| 196 |
On all the released versions of Solaris (8, 9 and 10) you need to make sure the following packages are installed (this info is extracted from the Solaris FAQ): |
| 197 |
.PP |
| 198 |
for tools (sccs, lex, yacc, make, nm, truss, ld, as): SUNWbtool, |
| 199 |
SUNWsprot, SUNWtoo |
| 200 |
.PP |
| 201 |
for libraries & headers: SUNWhea, SUNWarc, SUNWlibm, SUNWlibms, SUNWdfbh, |
| 202 |
SUNWcg6h, SUNWxwinc |
| 203 |
.PP |
| 204 |
Additionally, on Solaris 8 and 9 you also need: |
| 205 |
.PP |
| 206 |
for 64 bit development: SUNWarcx, SUNWbtoox, SUNWdplx, SUNWscpux, |
| 207 |
SUNWsprox, SUNWtoox, SUNWlmsx, SUNWlmx, SUNWlibCx |
| 208 |
.PP |
| 209 |
And only on Solaris 8 you also need: |
| 210 |
.PP |
| 211 |
for libraries & headers: SUNWolinc |
| 212 |
.PP |
| 213 |
If you are in doubt which package contains a file you are missing, |
| 214 |
try to find an installation that has that file. Then do a |
| 215 |
.PP |
| 216 |
.Vb 1 |
| 217 |
\& $ grep /my/missing/file /var/sadm/install/contents |
| 218 |
.Ve |
| 219 |
.PP |
| 220 |
This will display a line like this: |
| 221 |
.PP |
| 222 |
/usr/include/sys/errno.h f none 0644 root bin 7471 37605 956241356 SUNWhea |
| 223 |
.PP |
| 224 |
The last item listed (SUNWhea in this example) is the package you need. |
| 225 |
.PP |
| 226 |
\fIAvoid /usr/ucb/cc\fR |
| 227 |
.IX Subsection "Avoid /usr/ucb/cc" |
| 228 |
.PP |
| 229 |
You don't need to have /usr/ucb/ in your PATH to build perl. If you |
| 230 |
want /usr/ucb/ in your PATH anyway, make sure that /usr/ucb/ is NOT |
| 231 |
in your PATH before the directory containing the right C compiler. |
| 232 |
.PP |
| 233 |
\fISun's C Compiler\fR |
| 234 |
.IX Subsection "Sun's C Compiler" |
| 235 |
.PP |
| 236 |
If you use Sun's C compiler, make sure the correct directory |
| 237 |
(usually /opt/SUNWspro/bin/) is in your PATH (before /usr/ucb/). |
| 238 |
.PP |
| 239 |
\fIGCC\fR |
| 240 |
.IX Subsection "GCC" |
| 241 |
.PP |
| 242 |
If you use gcc, make sure your installation is recent and complete. |
| 243 |
perl versions since 5.6.0 build fine with gcc > 2.8.1 on Solaris >= |
| 244 |
2.6. |
| 245 |
.PP |
| 246 |
You must Configure perl with |
| 247 |
.PP |
| 248 |
.Vb 1 |
| 249 |
\& $ sh Configure \-Dcc=gcc |
| 250 |
.Ve |
| 251 |
.PP |
| 252 |
If you don't, you may experience strange build errors. |
| 253 |
.PP |
| 254 |
If you have updated your Solaris version, you may also have to update |
| 255 |
your gcc. For example, if you are running Solaris 2.6 and your gcc is |
| 256 |
installed under /usr/local, check in /usr/local/lib/gcc\-lib and make |
| 257 |
sure you have the appropriate directory, sparc\-sun\-solaris2.6/ or |
| 258 |
i386\-pc\-solaris2.6/. If gcc's directory is for a different version of |
| 259 |
Solaris than you are running, then you will need to rebuild gcc for |
| 260 |
your new version of Solaris. |
| 261 |
.PP |
| 262 |
You can get a precompiled version of gcc from |
| 263 |
<http://www.sunfreeware.com/> or <http://www.blastwave.org/>. Make |
| 264 |
sure you pick up the package for your Solaris release. |
| 265 |
.PP |
| 266 |
If you wish to use gcc to build add-on modules for use with the perl |
| 267 |
shipped with Solaris, you should use the Solaris::PerlGcc module |
| 268 |
which is available from CPAN. The perl shipped with Solaris |
| 269 |
is configured and built with the Sun compilers, and the compiler |
| 270 |
configuration information stored in Config.pm is therefore only |
| 271 |
relevant to the Sun compilers. The Solaris:PerlGcc module contains a |
| 272 |
replacement Config.pm that is correct for gcc \- see the module for |
| 273 |
details. |
| 274 |
.PP |
| 275 |
\fIGNU as and GNU ld\fR |
| 276 |
.IX Subsection "GNU as and GNU ld" |
| 277 |
.PP |
| 278 |
The following information applies to gcc version 2. Volunteers to |
| 279 |
update it as appropriately for gcc version 3 would be appreciated. |
| 280 |
.PP |
| 281 |
The versions of as and ld supplied with Solaris work fine for building |
| 282 |
perl. There is normally no need to install the GNU versions to |
| 283 |
compile perl. |
| 284 |
.PP |
| 285 |
If you decide to ignore this advice and use the GNU versions anyway, |
| 286 |
then be sure that they are relatively recent. Versions newer than 2.7 |
| 287 |
are apparently new enough. Older versions may have trouble with |
| 288 |
dynamic loading. |
| 289 |
.PP |
| 290 |
If you wish to use GNU ld, then you need to pass it the \-Wl,\-E flag. |
| 291 |
The hints/solaris_2.sh file tries to do this automatically by setting |
| 292 |
the following Configure variables: |
| 293 |
.PP |
| 294 |
.Vb 2 |
| 295 |
\& ccdlflags="$ccdlflags \-Wl,\-E" |
| 296 |
\& lddlflags="$lddlflags \-Wl,\-E \-G" |
| 297 |
.Ve |
| 298 |
.PP |
| 299 |
However, over the years, changes in gcc, GNU ld, and Solaris ld have made |
| 300 |
it difficult to automatically detect which ld ultimately gets called. |
| 301 |
You may have to manually edit config.sh and add the \-Wl,\-E flags |
| 302 |
yourself, or else run Configure interactively and add the flags at the |
| 303 |
appropriate prompts. |
| 304 |
.PP |
| 305 |
If your gcc is configured to use GNU as and ld but you want to use the |
| 306 |
Solaris ones instead to build perl, then you'll need to add |
| 307 |
\&\-B/usr/ccs/bin/ to the gcc command line. One convenient way to do |
| 308 |
that is with |
| 309 |
.PP |
| 310 |
.Vb 1 |
| 311 |
\& $ sh Configure \-Dcc=\*(Aqgcc \-B/usr/ccs/bin/\*(Aq |
| 312 |
.Ve |
| 313 |
.PP |
| 314 |
Note that the trailing slash is required. This will result in some |
| 315 |
harmless warnings as Configure is run: |
| 316 |
.PP |
| 317 |
.Vb 1 |
| 318 |
\& gcc: file path prefix \`/usr/ccs/bin/\*(Aq never used |
| 319 |
.Ve |
| 320 |
.PP |
| 321 |
These messages may safely be ignored. |
| 322 |
(Note that for a SunOS4 system, you must use \-B/bin/ instead.) |
| 323 |
.PP |
| 324 |
Alternatively, you can use the GCC_EXEC_PREFIX environment variable to |
| 325 |
ensure that Sun's as and ld are used. Consult your gcc documentation |
| 326 |
for further information on the \-B option and the GCC_EXEC_PREFIX variable. |
| 327 |
.PP |
| 328 |
\fISun and GNU make\fR |
| 329 |
.IX Subsection "Sun and GNU make" |
| 330 |
.PP |
| 331 |
The make under /usr/ccs/bin works fine for building perl. If you |
| 332 |
have the Sun C compilers, you will also have a parallel version of |
| 333 |
make (dmake). This works fine to build perl, but can sometimes cause |
| 334 |
problems when running 'make test' due to underspecified dependencies |
| 335 |
between the different test harness files. The same problem can also |
| 336 |
affect the building of some add-on modules, so in those cases either |
| 337 |
specify '\-m serial' on the dmake command line, or use |
| 338 |
/usr/ccs/bin/make instead. If you wish to use GNU make, be sure that |
| 339 |
the set-group-id bit is not set. If it is, then arrange your PATH so |
| 340 |
that /usr/ccs/bin/make is before GNU make or else have the system |
| 341 |
administrator disable the set-group-id bit on GNU make. |
| 342 |
.PP |
| 343 |
\fIAvoid libucb\fR |
| 344 |
.IX Subsection "Avoid libucb" |
| 345 |
.PP |
| 346 |
Solaris provides some BSD-compatibility functions in /usr/ucblib/libucb.a. |
| 347 |
Perl will not build and run correctly if linked against \-lucb since it |
| 348 |
contains routines that are incompatible with the standard Solaris libc. |
| 349 |
Normally this is not a problem since the solaris hints file prevents |
| 350 |
Configure from even looking in /usr/ucblib for libraries, and also |
| 351 |
explicitly omits \-lucb. |
| 352 |
.SS "Environment for Compiling perl on Solaris" |
| 353 |
.IX Subsection "Environment for Compiling perl on Solaris" |
| 354 |
\fIPATH\fR |
| 355 |
.IX Subsection "PATH" |
| 356 |
.PP |
| 357 |
Make sure your PATH includes the compiler (/opt/SUNWspro/bin/ if you're |
| 358 |
using Sun's compiler) as well as /usr/ccs/bin/ to pick up the other |
| 359 |
development tools (such as make, ar, as, and ld). Make sure your path |
| 360 |
either doesn't include /usr/ucb or that it includes it after the |
| 361 |
compiler and compiler tools and other standard Solaris directories. |
| 362 |
You definitely don't want /usr/ucb/cc. |
| 363 |
.PP |
| 364 |
\fILD_LIBRARY_PATH\fR |
| 365 |
.IX Subsection "LD_LIBRARY_PATH" |
| 366 |
.PP |
| 367 |
If you have the LD_LIBRARY_PATH environment variable set, be sure that |
| 368 |
it does NOT include /lib or /usr/lib. If you will be building |
| 369 |
extensions that call third-party shared libraries (e.g. Berkeley DB) |
| 370 |
then make sure that your LD_LIBRARY_PATH environment variable includes |
| 371 |
the directory with that library (e.g. /usr/local/lib). |
| 372 |
.PP |
| 373 |
If you get an error message |
| 374 |
.PP |
| 375 |
.Vb 1 |
| 376 |
\& dlopen: stub interception failed |
| 377 |
.Ve |
| 378 |
.PP |
| 379 |
it is probably because your LD_LIBRARY_PATH environment variable |
| 380 |
includes a directory which is a symlink to /usr/lib (such as /lib). |
| 381 |
The reason this causes a problem is quite subtle. The file |
| 382 |
libdl.so.1.0 actually *only* contains functions which generate 'stub |
| 383 |
interception failed' errors! The runtime linker intercepts links to |
| 384 |
"/usr/lib/libdl.so.1.0" and links in internal implementations of those |
| 385 |
functions instead. [Thanks to Tim Bunce for this explanation.] |
| 386 |
.SH "RUN CONFIGURE" |
| 387 |
.IX Header "RUN CONFIGURE" |
| 388 |
See the INSTALL file for general information regarding Configure. |
| 389 |
Only Solaris-specific issues are discussed here. Usually, the |
| 390 |
defaults should be fine. |
| 391 |
.SS "64\-bit perl on Solaris" |
| 392 |
.IX Subsection "64-bit perl on Solaris" |
| 393 |
See the INSTALL file for general information regarding 64\-bit compiles. |
| 394 |
In general, the defaults should be fine for most people. |
| 395 |
.PP |
| 396 |
By default, perl\-5.6.0 (or later) is compiled as a 32\-bit application |
| 397 |
with largefile and long-long support. |
| 398 |
.PP |
| 399 |
\fIGeneral 32\-bit vs. 64\-bit issues\fR |
| 400 |
.IX Subsection "General 32-bit vs. 64-bit issues" |
| 401 |
.PP |
| 402 |
Solaris 7 and above will run in either 32 bit or 64 bit mode on SPARC |
| 403 |
CPUs, via a reboot. You can build 64 bit apps whilst running 32 bit |
| 404 |
mode and vice-versa. 32 bit apps will run under Solaris running in |
| 405 |
either 32 or 64 bit mode. 64 bit apps require Solaris to be running |
| 406 |
64 bit mode. |
| 407 |
.PP |
| 408 |
Existing 32 bit apps are properly known as LP32, i.e. Longs and |
| 409 |
Pointers are 32 bit. 64\-bit apps are more properly known as LP64. |
| 410 |
The discriminating feature of a LP64 bit app is its ability to utilise a |
| 411 |
64\-bit address space. It is perfectly possible to have a LP32 bit app |
| 412 |
that supports both 64\-bit integers (long long) and largefiles (> 2GB), |
| 413 |
and this is the default for perl\-5.6.0. |
| 414 |
.PP |
| 415 |
For a more complete explanation of 64\-bit issues, see the |
| 416 |
"Solaris 64\-bit Developer's Guide" at <http://docs.sun.com/> |
| 417 |
.PP |
| 418 |
You can detect the OS mode using "isainfo \-v", e.g. |
| 419 |
.PP |
| 420 |
.Vb 3 |
| 421 |
\& $ isainfo \-v # Ultra 30 in 64 bit mode |
| 422 |
\& 64\-bit sparcv9 applications |
| 423 |
\& 32\-bit sparc applications |
| 424 |
.Ve |
| 425 |
.PP |
| 426 |
By default, perl will be compiled as a 32\-bit application. Unless |
| 427 |
you want to allocate more than ~ 4GB of memory inside perl, or unless |
| 428 |
you need more than 255 open file descriptors, you probably don't need |
| 429 |
perl to be a 64\-bit app. |
| 430 |
.PP |
| 431 |
\fILarge File Support\fR |
| 432 |
.IX Subsection "Large File Support" |
| 433 |
.PP |
| 434 |
For Solaris 2.6 and onwards, there are two different ways for 32\-bit |
| 435 |
applications to manipulate large files (files whose size is > 2GByte). |
| 436 |
(A 64\-bit application automatically has largefile support built in |
| 437 |
by default.) |
| 438 |
.PP |
| 439 |
First is the "transitional compilation environment", described in |
| 440 |
\&\fBlfcompile64\fR\|(5). According to the man page, |
| 441 |
.PP |
| 442 |
.Vb 7 |
| 443 |
\& The transitional compilation environment exports all the |
| 444 |
\& explicit 64\-bit functions (xxx64()) and types in addition to |
| 445 |
\& all the regular functions (xxx()) and types. Both xxx() and |
| 446 |
\& xxx64() functions are available to the program source. A |
| 447 |
\& 32\-bit application must use the xxx64() functions in order |
| 448 |
\& to access large files. See the lf64(5) manual page for a |
| 449 |
\& complete listing of the 64\-bit transitional interfaces. |
| 450 |
.Ve |
| 451 |
.PP |
| 452 |
The transitional compilation environment is obtained with the |
| 453 |
following compiler and linker flags: |
| 454 |
.PP |
| 455 |
.Vb 3 |
| 456 |
\& getconf LFS64_CFLAGS \-D_LARGEFILE64_SOURCE |
| 457 |
\& getconf LFS64_LDFLAG # nothing special needed |
| 458 |
\& getconf LFS64_LIBS # nothing special needed |
| 459 |
.Ve |
| 460 |
.PP |
| 461 |
Second is the "large file compilation environment", described in |
| 462 |
\&\fBlfcompile\fR\|(5). According to the man page, |
| 463 |
.PP |
| 464 |
.Vb 5 |
| 465 |
\& Each interface named xxx() that needs to access 64\-bit entities |
| 466 |
\& to access large files maps to a xxx64() call in the |
| 467 |
\& resulting binary. All relevant data types are defined to be |
| 468 |
\& of correct size (for example, off_t has a typedef definition |
| 469 |
\& for a 64\-bit entity). |
| 470 |
\& |
| 471 |
\& An application compiled in this environment is able to use |
| 472 |
\& the xxx() source interfaces to access both large and small |
| 473 |
\& files, rather than having to explicitly utilize the transitional |
| 474 |
\& xxx64() interface calls to access large files. |
| 475 |
.Ve |
| 476 |
.PP |
| 477 |
Two exceptions are \fBfseek()\fR and \fBftell()\fR. 32\-bit applications should |
| 478 |
use fseeko(3C) and ftello(3C). These will get automatically mapped |
| 479 |
to \fBfseeko64()\fR and \fBftello64()\fR. |
| 480 |
.PP |
| 481 |
The large file compilation environment is obtained with |
| 482 |
.PP |
| 483 |
.Vb 3 |
| 484 |
\& getconf LFS_CFLAGS \-D_LARGEFILE_SOURCE \-D_FILE_OFFSET_BITS=64 |
| 485 |
\& getconf LFS_LDFLAGS # nothing special needed |
| 486 |
\& getconf LFS_LIBS # nothing special needed |
| 487 |
.Ve |
| 488 |
.PP |
| 489 |
By default, perl uses the large file compilation environment and |
| 490 |
relies on Solaris to do the underlying mapping of interfaces. |
| 491 |
.PP |
| 492 |
\fIBuilding an LP64 perl\fR |
| 493 |
.IX Subsection "Building an LP64 perl" |
| 494 |
.PP |
| 495 |
To compile a 64\-bit application on an UltraSparc with a recent Sun Compiler, |
| 496 |
you need to use the flag "\-xarch=v9". \fBgetconf\fR\|(1) will tell you this, e.g. |
| 497 |
.PP |
| 498 |
.Vb 10 |
| 499 |
\& $ getconf \-a | grep v9 |
| 500 |
\& XBS5_LP64_OFF64_CFLAGS: \-xarch=v9 |
| 501 |
\& XBS5_LP64_OFF64_LDFLAGS: \-xarch=v9 |
| 502 |
\& XBS5_LP64_OFF64_LINTFLAGS: \-xarch=v9 |
| 503 |
\& XBS5_LPBIG_OFFBIG_CFLAGS: \-xarch=v9 |
| 504 |
\& XBS5_LPBIG_OFFBIG_LDFLAGS: \-xarch=v9 |
| 505 |
\& XBS5_LPBIG_OFFBIG_LINTFLAGS: \-xarch=v9 |
| 506 |
\& _XBS5_LP64_OFF64_CFLAGS: \-xarch=v9 |
| 507 |
\& _XBS5_LP64_OFF64_LDFLAGS: \-xarch=v9 |
| 508 |
\& _XBS5_LP64_OFF64_LINTFLAGS: \-xarch=v9 |
| 509 |
\& _XBS5_LPBIG_OFFBIG_CFLAGS: \-xarch=v9 |
| 510 |
\& _XBS5_LPBIG_OFFBIG_LDFLAGS: \-xarch=v9 |
| 511 |
\& _XBS5_LPBIG_OFFBIG_LINTFLAGS: \-xarch=v9 |
| 512 |
.Ve |
| 513 |
.PP |
| 514 |
This flag is supported in Sun WorkShop Compilers 5.0 and onwards |
| 515 |
(now marketed under the name Forte) when used on Solaris 7 or later on |
| 516 |
UltraSparc systems. |
| 517 |
.PP |
| 518 |
If you are using gcc, you would need to use \-mcpu=v9 \-m64 instead. This |
| 519 |
option is not yet supported as of gcc 2.95.2; from install/SPECIFIC |
| 520 |
in that release: |
| 521 |
.PP |
| 522 |
.Vb 5 |
| 523 |
\& GCC version 2.95 is not able to compile code correctly for sparc64 |
| 524 |
\& targets. Users of the Linux kernel, at least, can use the sparc32 |
| 525 |
\& program to start up a new shell invocation with an environment that |
| 526 |
\& causes configure to recognize (via uname \-a) the system as sparc\-*\-* |
| 527 |
\& instead. |
| 528 |
.Ve |
| 529 |
.PP |
| 530 |
All this should be handled automatically by the hints file, if |
| 531 |
requested. |
| 532 |
.PP |
| 533 |
\fILong Doubles\fR |
| 534 |
.IX Subsection "Long Doubles" |
| 535 |
.PP |
| 536 |
As of 5.8.1, long doubles are working if you use the Sun compilers |
| 537 |
(needed for additional math routines not included in libm). |
| 538 |
.SS "Threads in perl on Solaris" |
| 539 |
.IX Subsection "Threads in perl on Solaris" |
| 540 |
It is possible to build a threaded version of perl on Solaris. The entire |
| 541 |
perl thread implementation is still experimental, however, so beware. |
| 542 |
.SS "Malloc Issues with perl on Solaris" |
| 543 |
.IX Subsection "Malloc Issues with perl on Solaris" |
| 544 |
Starting from perl 5.7.1 perl uses the Solaris malloc, since the perl |
| 545 |
malloc breaks when dealing with more than 2GB of memory, and the Solaris |
| 546 |
malloc also seems to be faster. |
| 547 |
.PP |
| 548 |
If you for some reason (such as binary backward compatibility) really |
| 549 |
need to use perl's malloc, you can rebuild perl from the sources |
| 550 |
and Configure the build with |
| 551 |
.PP |
| 552 |
.Vb 1 |
| 553 |
\& $ sh Configure \-Dusemymalloc |
| 554 |
.Ve |
| 555 |
.PP |
| 556 |
You should not use perl's malloc if you are building with gcc. There |
| 557 |
are reports of core dumps, especially in the PDL module. The problem |
| 558 |
appears to go away under \-DDEBUGGING, so it has been difficult to |
| 559 |
track down. Sun's compiler appears to be okay with or without perl's |
| 560 |
malloc. [XXX further investigation is needed here.] |
| 561 |
.SH "MAKE PROBLEMS" |
| 562 |
.IX Header "MAKE PROBLEMS" |
| 563 |
.IP "Dynamic Loading Problems With GNU as and GNU ld" 4 |
| 564 |
.IX Item "Dynamic Loading Problems With GNU as and GNU ld" |
| 565 |
If you have problems with dynamic loading using gcc on SunOS or |
| 566 |
Solaris, and you are using GNU as and GNU ld, see the section |
| 567 |
"GNU as and GNU ld" above. |
| 568 |
.IP "ld.so.1: ./perl: fatal: relocation error:" 4 |
| 569 |
.IX Item "ld.so.1: ./perl: fatal: relocation error:" |
| 570 |
If you get this message on SunOS or Solaris, and you're using gcc, |
| 571 |
it's probably the GNU as or GNU ld problem in the previous item |
| 572 |
"GNU as and GNU ld". |
| 573 |
.IP "dlopen: stub interception failed" 4 |
| 574 |
.IX Item "dlopen: stub interception failed" |
| 575 |
The primary cause of the 'dlopen: stub interception failed' message is |
| 576 |
that the LD_LIBRARY_PATH environment variable includes a directory |
| 577 |
which is a symlink to /usr/lib (such as /lib). See |
| 578 |
"LD_LIBRARY_PATH" above. |
| 579 |
.IP "#error ""No DATAMODEL_NATIVE specified""" 4 |
| 580 |
.IX Item "#error ""No DATAMODEL_NATIVE specified""" |
| 581 |
This is a common error when trying to build perl on Solaris 2.6 with a |
| 582 |
gcc installation from Solaris 2.5 or 2.5.1. The Solaris header files |
| 583 |
changed, so you need to update your gcc installation. You can either |
| 584 |
rerun the fixincludes script from gcc or take the opportunity to |
| 585 |
update your gcc installation. |
| 586 |
.IP "sh: ar: not found" 4 |
| 587 |
.IX Item "sh: ar: not found" |
| 588 |
This is a message from your shell telling you that the command 'ar' |
| 589 |
was not found. You need to check your PATH environment variable to |
| 590 |
make sure that it includes the directory with the 'ar' command. This |
| 591 |
is a common problem on Solaris, where 'ar' is in the /usr/ccs/bin/ |
| 592 |
directory. |
| 593 |
.SH "MAKE TEST" |
| 594 |
.IX Header "MAKE TEST" |
| 595 |
.SS "op/stat.t test 4 in Solaris" |
| 596 |
.IX Subsection "op/stat.t test 4 in Solaris" |
| 597 |
\&\fIop/stat.t\fR test 4 may fail if you are on a tmpfs of some sort. |
| 598 |
Building in /tmp sometimes shows this behavior. The |
| 599 |
test suite detects if you are building in /tmp, but it may not be able |
| 600 |
to catch all tmpfs situations. |
| 601 |
.SS "nss_delete core dump from op/pwent or op/grent" |
| 602 |
.IX Subsection "nss_delete core dump from op/pwent or op/grent" |
| 603 |
See "nss_delete core dump from op/pwent or op/grent" in perlhpux. |
| 604 |
.SH CROSS-COMPILATION |
| 605 |
.IX Header "CROSS-COMPILATION" |
| 606 |
Nothing too unusual here. You can easily do this if you have a |
| 607 |
cross-compiler available; A usual Configure invocation when targetting a |
| 608 |
Solaris x86 looks something like this: |
| 609 |
.PP |
| 610 |
.Vb 5 |
| 611 |
\& sh ./Configure \-des \-Dusecrosscompile \e |
| 612 |
\& \-Dcc=i386\-pc\-solaris2.11\-gcc \e |
| 613 |
\& \-Dsysroot=$SYSROOT \e |
| 614 |
\& \-Alddlflags=" \-Wl,\-z,notext" \e |
| 615 |
\& \-Dtargethost=... # The usual cross\-compilation options |
| 616 |
.Ve |
| 617 |
.PP |
| 618 |
The lddlflags addition is the only abnormal bit. |
| 619 |
.SH "PREBUILT BINARIES OF PERL FOR SOLARIS" |
| 620 |
.IX Header "PREBUILT BINARIES OF PERL FOR SOLARIS" |
| 621 |
You can pick up prebuilt binaries for Solaris from |
| 622 |
<http://www.sunfreeware.com/>, <http://www.blastwave.org>, |
| 623 |
ActiveState <http://www.activestate.com/>, and |
| 624 |
<http://www.perl.com/> under the Binaries list at the top of the |
| 625 |
page. There are probably other sources as well. Please note that |
| 626 |
these sites are under the control of their respective owners, not the |
| 627 |
perl developers. |
| 628 |
.SH "RUNTIME ISSUES FOR PERL ON SOLARIS" |
| 629 |
.IX Header "RUNTIME ISSUES FOR PERL ON SOLARIS" |
| 630 |
.SS "Limits on Numbers of Open Files on Solaris" |
| 631 |
.IX Subsection "Limits on Numbers of Open Files on Solaris" |
| 632 |
The stdio(3C) manpage notes that for LP32 applications, only 255 |
| 633 |
files may be opened using \fBfopen()\fR, and only file descriptors 0 |
| 634 |
through 255 can be used in a stream. Since perl calls \fBopen()\fR and |
| 635 |
then fdopen(3C) with the resulting file descriptor, perl is limited |
| 636 |
to 255 simultaneous open files, even if \fBsysopen()\fR is used. If this |
| 637 |
proves to be an insurmountable problem, you can compile perl as a |
| 638 |
LP64 application, see "Building an LP64 perl" for details. Note |
| 639 |
also that the default resource limit for open file descriptors on |
| 640 |
Solaris is 255, so you will have to modify your ulimit or rctl |
| 641 |
(Solaris 9 onwards) appropriately. |
| 642 |
.SH "SOLARIS-SPECIFIC MODULES" |
| 643 |
.IX Header "SOLARIS-SPECIFIC MODULES" |
| 644 |
See the modules under the Solaris:: and Sun::Solaris namespaces on CPAN, |
| 645 |
see <http://www.cpan.org/modules/by\-module/Solaris/> and |
| 646 |
<http://www.cpan.org/modules/by\-module/Sun/>. |
| 647 |
.SH "SOLARIS-SPECIFIC PROBLEMS WITH MODULES" |
| 648 |
.IX Header "SOLARIS-SPECIFIC PROBLEMS WITH MODULES" |
| 649 |
.SS "Proc::ProcessTable on Solaris" |
| 650 |
.IX Subsection "Proc::ProcessTable on Solaris" |
| 651 |
Proc::ProcessTable does not compile on Solaris with perl5.6.0 and higher |
| 652 |
if you have LARGEFILES defined. Since largefile support is the |
| 653 |
default in 5.6.0 and later, you have to take special steps to use this |
| 654 |
module. |
| 655 |
.PP |
| 656 |
The problem is that various structures visible via procfs use off_t, |
| 657 |
and if you compile with largefile support these change from 32 bits to |
| 658 |
64 bits. Thus what you get back from procfs doesn't match up with |
| 659 |
the structures in perl, resulting in garbage. See \fBproc\fR\|(4) for further |
| 660 |
discussion. |
| 661 |
.PP |
| 662 |
A fix for Proc::ProcessTable is to edit Makefile to |
| 663 |
explicitly remove the largefile flags from the ones MakeMaker picks up |
| 664 |
from Config.pm. This will result in Proc::ProcessTable being built |
| 665 |
under the correct environment. Everything should then be OK as long as |
| 666 |
Proc::ProcessTable doesn't try to share off_t's with the rest of perl, |
| 667 |
or if it does they should be explicitly specified as off64_t. |
| 668 |
.SS "BSD::Resource on Solaris" |
| 669 |
.IX Subsection "BSD::Resource on Solaris" |
| 670 |
BSD::Resource versions earlier than 1.09 do not compile on Solaris |
| 671 |
with perl 5.6.0 and higher, for the same reasons as Proc::ProcessTable. |
| 672 |
BSD::Resource versions starting from 1.09 have a workaround for the problem. |
| 673 |
.SS "Net::SSLeay on Solaris" |
| 674 |
.IX Subsection "Net::SSLeay on Solaris" |
| 675 |
Net::SSLeay requires a /dev/urandom to be present. This device is |
| 676 |
available from Solaris 9 onwards. For earlier Solaris versions you |
| 677 |
can either get the package SUNWski (packaged with several Sun |
| 678 |
software products, for example the Sun WebServer, which is part of |
| 679 |
the Solaris Server Intranet Extension, or the Sun Directory Services, |
| 680 |
part of Solaris for ISPs) or download the ANDIrand package from |
| 681 |
<http://www.cosy.sbg.ac.at/~andi/>. If you use SUNWski, make a |
| 682 |
symbolic link /dev/urandom pointing to /dev/random. For more details, |
| 683 |
see Document ID27606 entitled "Differing /dev/random support requirements |
| 684 |
within Solaris[TM] Operating Environments", available at |
| 685 |
<http://sunsolve.sun.com> . |
| 686 |
.PP |
| 687 |
It may be possible to use the Entropy Gathering Daemon (written in |
| 688 |
Perl!), available from <http://www.lothar.com/tech/crypto/>. |
| 689 |
.SH "SunOS 4.x" |
| 690 |
.IX Header "SunOS 4.x" |
| 691 |
In SunOS 4.x you most probably want to use the SunOS ld, /usr/bin/ld, |
| 692 |
since the more recent versions of GNU ld (like 2.13) do not seem to |
| 693 |
work for building Perl anymore. When linking the extensions, the |
| 694 |
GNU ld gets very unhappy and spews a lot of errors like this |
| 695 |
.PP |
| 696 |
.Vb 1 |
| 697 |
\& ... relocation truncated to fit: BASE13 ... |
| 698 |
.Ve |
| 699 |
.PP |
| 700 |
and dies. Therefore the SunOS 4.1 hints file explicitly sets the |
| 701 |
ld to be \fI/usr/bin/ld\fR. |
| 702 |
.PP |
| 703 |
As of Perl 5.8.1 the dynamic loading of libraries (DynaLoader, XSLoader) |
| 704 |
also seems to have become broken in in SunOS 4.x. Therefore the default |
| 705 |
is to build Perl statically. |
| 706 |
.PP |
| 707 |
Running the test suite in SunOS 4.1 is a bit tricky since the |
| 708 |
\&\fIdist/Tie\-File/t/09_gen_rs.t\fR test hangs (subtest #51, FWIW) for some |
| 709 |
unknown reason. Just stop the test and kill that particular Perl |
| 710 |
process. |
| 711 |
.PP |
| 712 |
There are various other failures, that as of SunOS 4.1.4 and gcc 3.2.2 |
| 713 |
look a lot like gcc bugs. Many of the failures happen in the Encode |
| 714 |
tests, where for example when the test expects "0" you get "0" |
| 715 |
which should after a little squinting look very odd indeed. |
| 716 |
Another example is earlier in \fIt/run/fresh_perl\fR where \fBchr\fR\|(0xff) is |
| 717 |
expected but the test fails because the result is \fBchr\fR\|(0xff). Exactly. |
| 718 |
.PP |
| 719 |
This is the "make test" result from the said combination: |
| 720 |
.PP |
| 721 |
.Vb 1 |
| 722 |
\& Failed 27 test scripts out of 745, 96.38% okay. |
| 723 |
.Ve |
| 724 |
.PP |
| 725 |
Running the \f(CW\*(C`harness\*(C'\fR is painful because of the many failing |
| 726 |
Unicode-related tests will output megabytes of failure messages, |
| 727 |
but if one patiently waits, one gets these results: |
| 728 |
.PP |
| 729 |
.Vb 10 |
| 730 |
\& Failed Test Stat Wstat Total Fail Failed List of Failed |
| 731 |
\& \-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\- |
| 732 |
\& ... |
| 733 |
\& ../ext/Encode/t/at\-cn.t 4 1024 29 4 13.79% 14\-17 |
| 734 |
\& ../ext/Encode/t/at\-tw.t 10 2560 17 10 58.82% 2 4 6 8 10 12 |
| 735 |
\& 14\-17 |
| 736 |
\& ../ext/Encode/t/enc_data.t 29 7424 ?? ?? % ?? |
| 737 |
\& ../ext/Encode/t/enc_eucjp.t 29 7424 ?? ?? % ?? |
| 738 |
\& ../ext/Encode/t/enc_module.t 29 7424 ?? ?? % ?? |
| 739 |
\& ../ext/Encode/t/encoding.t 29 7424 ?? ?? % ?? |
| 740 |
\& ../ext/Encode/t/grow.t 12 3072 24 12 50.00% 2 4 6 8 10 12 14 |
| 741 |
\& 16 18 20 22 24 |
| 742 |
\& Failed Test Stat Wstat Total Fail Failed List of Failed |
| 743 |
\& \-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\- |
| 744 |
\& ../ext/Encode/t/guess.t 255 65280 29 40 137.93% 10\-29 |
| 745 |
\& ../ext/Encode/t/jperl.t 29 7424 15 30 200.00% 1\-15 |
| 746 |
\& ../ext/Encode/t/mime\-header.t 2 512 10 2 20.00% 2\-3 |
| 747 |
\& ../ext/Encode/t/perlio.t 22 5632 38 22 57.89% 1\-4 9\-16 19\-20 |
| 748 |
\& 23\-24 27\-32 |
| 749 |
\& ../ext/List/Util/t/shuffle.t 0 139 ?? ?? % ?? |
| 750 |
\& ../ext/PerlIO/t/encoding.t 14 1 7.14% 11 |
| 751 |
\& ../ext/PerlIO/t/fallback.t 9 2 22.22% 3 5 |
| 752 |
\& ../ext/Socket/t/socketpair.t 0 2 45 70 155.56% 11\-45 |
| 753 |
\& ../lib/CPAN/t/vcmp.t 30 1 3.33% 25 |
| 754 |
\& ../lib/Tie/File/t/09_gen_rs.t 0 15 ?? ?? % ?? |
| 755 |
\& ../lib/Unicode/Collate/t/test.t 199 30 15.08% 7 26\-27 71\-75 |
| 756 |
\& 81\-88 95 101 |
| 757 |
\& 103\-104 106 108\- |
| 758 |
\& 109 122 124 161 |
| 759 |
\& 169\-172 |
| 760 |
\& ../lib/sort.t 0 139 119 26 21.85% 107\-119 |
| 761 |
\& op/alarm.t 4 1 25.00% 4 |
| 762 |
\& op/utfhash.t 97 1 1.03% 31 |
| 763 |
\& run/fresh_perl.t 91 1 1.10% 32 |
| 764 |
\& uni/tr_7jis.t ?? ?? % ?? |
| 765 |
\& uni/tr_eucjp.t 29 7424 6 12 200.00% 1\-6 |
| 766 |
\& uni/tr_sjis.t 29 7424 6 12 200.00% 1\-6 |
| 767 |
\& 56 tests and 467 subtests skipped. |
| 768 |
\& Failed 27/811 test scripts, 96.67% okay. 1383/75399 subtests failed, |
| 769 |
\& 98.17% okay. |
| 770 |
.Ve |
| 771 |
.PP |
| 772 |
The \fBalarm()\fR test failure is caused by \fBsystem()\fR apparently blocking |
| 773 |
\&\fBalarm()\fR. That is probably a libc bug, and given that SunOS 4.x |
| 774 |
has been end-of-lifed years ago, don't hold your breath for a fix. |
| 775 |
In addition to that, don't try anything too Unicode-y, especially |
| 776 |
with Encode, and you should be fine in SunOS 4.x. |
| 777 |
.SH AUTHOR |
| 778 |
.IX Header "AUTHOR" |
| 779 |
The original was written by Andy Dougherty \[email protected]\fR |
| 780 |
drawing heavily on advice from Alan Burlison, Nick Ing-Simmons, Tim Bunce, |
| 781 |
and many other Solaris users over the years. |
| 782 |
.PP |
| 783 |
Please report any errors, updates, or suggestions to |
| 784 |
<https://github.com/Perl/perl5/issues>. |