3 If you read this file _as_is_, just ignore the funny characters you
4 see. It is written in the POD format (see pod/perlpod.pod) which is
5 specifically designed to be readable as is.
9 perlsolaris - Perl version 5 on Solaris systems
13 This document describes various features of Sun's Solaris operating system
14 that will affect how Perl version 5 (hereafter just perl) is
15 compiled and/or runs. Some issues relating to the older SunOS 4.x are
16 also discussed, though they may be out of date.
18 For the most part, everything should just work.
20 Starting with Solaris 8, perl5.00503 (or higher) is supplied with the
21 operating system, so you might not even need to build a newer version
22 of perl at all. The Sun-supplied version is installed in /usr/perl5
23 with F</usr/bin/perl> pointing to F</usr/perl5/bin/perl>. Do not disturb
24 that installation unless you really know what you are doing. If you
25 remove the perl supplied with the OS, you will render some bits of
26 your system inoperable. If you wish to install a newer version of perl,
27 install it under a different prefix from /usr/perl5. Common prefixes
28 to use are /usr/local and /opt/perl.
30 You may wish to put your version of perl in the PATH of all users by
31 changing the link F</usr/bin/perl>. This is probably OK, as most perl
32 scripts shipped with Solaris use an explicit path. (There are a few
33 exceptions, such as F</usr/bin/rpm2cpio> and F</etc/rcm/scripts/README>, but
34 these are also sufficiently generic that the actual version of perl
35 probably doesn't matter too much.)
37 Solaris ships with a range of Solaris-specific modules. If you choose
38 to install your own version of perl you will find the source of many of
39 these modules is available on CPAN under the Sun::Solaris:: namespace.
41 Solaris may include two versions of perl, e.g. Solaris 9 includes
42 both 5.005_03 and 5.6.1. This is to provide stability across Solaris
43 releases, in cases where a later perl version has incompatibilities
44 with the version included in the preceding Solaris release. The
45 default perl version will always be the most recent, and in general
46 the old version will only be retained for one Solaris release. Note
47 also that the default perl will NOT be configured to search for modules
48 in the older version, again due to compatibility/stability concerns.
49 As a consequence if you upgrade Solaris, you will have to
50 rebuild/reinstall any additional CPAN modules that you installed for
51 the previous Solaris version. See the CPAN manpage under 'autobundle'
52 for a quick way of doing this.
54 As an interim measure, you may either change the #! line of your
55 scripts to specifically refer to the old perl version, e.g. on
56 Solaris 9 use #!/usr/perl5/5.00503/bin/perl to use the perl version
57 that was the default for Solaris 8, or if you have a large number of
58 scripts it may be more convenient to make the old version of perl the
59 default on your system. You can do this by changing the appropriate
60 symlinks under /usr/perl5 as follows (example for Solaris 9):
66 # ln -s ./5.00503/lib/pod
68 # ln -s ../perl5/5.00503/bin/perl /usr/bin/perl
70 In both cases this should only be considered to be a temporary
71 measure - you should upgrade to the later version of perl as soon as
74 Note also that the perl command-line utilities (e.g. perldoc) and any
75 that are added by modules that you install will be under
76 /usr/perl5/bin, so that directory should be added to your PATH.
78 =head2 Solaris Version Numbers
80 For consistency with common usage, perl's Configure script performs
81 some minor manipulations on the operating system name and version
82 number as reported by uname. Here's a partial translation table:
84 Sun: perl's Configure:
85 uname uname -r Name osname osvers
86 SunOS 4.1.3 Solaris 1.1 sunos 4.1.3
87 SunOS 5.6 Solaris 2.6 solaris 2.6
88 SunOS 5.8 Solaris 8 solaris 2.8
89 SunOS 5.9 Solaris 9 solaris 2.9
90 SunOS 5.10 Solaris 10 solaris 2.10
92 The complete table can be found in the Sun Managers' FAQ
93 L<ftp://ftp.cs.toronto.edu/pub/jdd/sunmanagers/faq> under
94 "9.1) Which Sun models run which versions of SunOS?".
98 There are many, many sources for Solaris information. A few of the
99 important ones for perl:
105 The Solaris FAQ is available at
106 L<http://www.science.uva.nl/pub/solaris/solaris2.html>.
108 The Sun Managers' FAQ is available at
109 L<ftp://ftp.cs.toronto.edu/pub/jdd/sunmanagers/faq>
111 =item Precompiled Binaries
113 Precompiled binaries, links to many sites, and much, much more are
114 available at L<http://www.sunfreeware.com/> and
115 L<http://www.blastwave.org/>.
117 =item Solaris Documentation
119 All Solaris documentation is available on-line at L<http://docs.sun.com/>.
125 =head2 File Extraction Problems on Solaris
127 Be sure to use a tar program compiled under Solaris (not SunOS 4.x)
128 to extract the perl-5.x.x.tar.gz file. Do not use GNU tar compiled
129 for SunOS4 on Solaris. (GNU tar compiled for Solaris should be fine.)
130 When you run SunOS4 binaries on Solaris, the run-time system magically
131 alters pathnames matching m#lib/locale# so that when tar tries to create
132 lib/locale.pm, a file named lib/oldlocale.pm gets created instead.
133 If you found this advice too late and used a SunOS4-compiled tar
134 anyway, you must find the incorrectly renamed file and move it back
137 =head2 Compiler and Related Tools on Solaris
139 You must use an ANSI C compiler to build perl. Perl can be compiled
140 with either Sun's add-on C compiler or with gcc. The C compiler that
141 shipped with SunOS4 will not do.
143 =head3 Include /usr/ccs/bin/ in your PATH
145 Several tools needed to build perl are located in /usr/ccs/bin/: ar,
146 as, ld, and make. Make sure that /usr/ccs/bin/ is in your PATH.
149 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):
151 for tools (sccs, lex, yacc, make, nm, truss, ld, as): SUNWbtool,
154 for libraries & headers: SUNWhea, SUNWarc, SUNWlibm, SUNWlibms, SUNWdfbh,
157 Additionally, on Solaris 8 and 9 you also need:
159 for 64 bit development: SUNWarcx, SUNWbtoox, SUNWdplx, SUNWscpux,
160 SUNWsprox, SUNWtoox, SUNWlmsx, SUNWlmx, SUNWlibCx
162 And only on Solaris 8 you also need:
164 for libraries & headers: SUNWolinc
167 If you are in doubt which package contains a file you are missing,
168 try to find an installation that has that file. Then do a
170 $ grep /my/missing/file /var/sadm/install/contents
172 This will display a line like this:
174 /usr/include/sys/errno.h f none 0644 root bin 7471 37605 956241356 SUNWhea
176 The last item listed (SUNWhea in this example) is the package you need.
178 =head3 Avoid /usr/ucb/cc
180 You don't need to have /usr/ucb/ in your PATH to build perl. If you
181 want /usr/ucb/ in your PATH anyway, make sure that /usr/ucb/ is NOT
182 in your PATH before the directory containing the right C compiler.
184 =head3 Sun's C Compiler
186 If you use Sun's C compiler, make sure the correct directory
187 (usually /opt/SUNWspro/bin/) is in your PATH (before /usr/ucb/).
191 If you use gcc, make sure your installation is recent and complete.
192 perl versions since 5.6.0 build fine with gcc > 2.8.1 on Solaris >=
195 You must Configure perl with
197 $ sh Configure -Dcc=gcc
199 If you don't, you may experience strange build errors.
201 If you have updated your Solaris version, you may also have to update
202 your gcc. For example, if you are running Solaris 2.6 and your gcc is
203 installed under /usr/local, check in /usr/local/lib/gcc-lib and make
204 sure you have the appropriate directory, sparc-sun-solaris2.6/ or
205 i386-pc-solaris2.6/. If gcc's directory is for a different version of
206 Solaris than you are running, then you will need to rebuild gcc for
207 your new version of Solaris.
209 You can get a precompiled version of gcc from
210 L<http://www.sunfreeware.com/> or L<http://www.blastwave.org/>. Make
211 sure you pick up the package for your Solaris release.
213 If you wish to use gcc to build add-on modules for use with the perl
214 shipped with Solaris, you should use the Solaris::PerlGcc module
215 which is available from CPAN. The perl shipped with Solaris
216 is configured and built with the Sun compilers, and the compiler
217 configuration information stored in Config.pm is therefore only
218 relevant to the Sun compilers. The Solaris:PerlGcc module contains a
219 replacement Config.pm that is correct for gcc - see the module for
222 =head3 GNU as and GNU ld
224 The following information applies to gcc version 2. Volunteers to
225 update it as appropriately for gcc version 3 would be appreciated.
227 The versions of as and ld supplied with Solaris work fine for building
228 perl. There is normally no need to install the GNU versions to
231 If you decide to ignore this advice and use the GNU versions anyway,
232 then be sure that they are relatively recent. Versions newer than 2.7
233 are apparently new enough. Older versions may have trouble with
236 If you wish to use GNU ld, then you need to pass it the -Wl,-E flag.
237 The hints/solaris_2.sh file tries to do this automatically by setting
238 the following Configure variables:
240 ccdlflags="$ccdlflags -Wl,-E"
241 lddlflags="$lddlflags -Wl,-E -G"
243 However, over the years, changes in gcc, GNU ld, and Solaris ld have made
244 it difficult to automatically detect which ld ultimately gets called.
245 You may have to manually edit config.sh and add the -Wl,-E flags
246 yourself, or else run Configure interactively and add the flags at the
249 If your gcc is configured to use GNU as and ld but you want to use the
250 Solaris ones instead to build perl, then you'll need to add
251 -B/usr/ccs/bin/ to the gcc command line. One convenient way to do
254 $ sh Configure -Dcc='gcc -B/usr/ccs/bin/'
256 Note that the trailing slash is required. This will result in some
257 harmless warnings as Configure is run:
259 gcc: file path prefix `/usr/ccs/bin/' never used
261 These messages may safely be ignored.
262 (Note that for a SunOS4 system, you must use -B/bin/ instead.)
264 Alternatively, you can use the GCC_EXEC_PREFIX environment variable to
265 ensure that Sun's as and ld are used. Consult your gcc documentation
266 for further information on the -B option and the GCC_EXEC_PREFIX variable.
268 =head3 Sun and GNU make
270 The make under /usr/ccs/bin works fine for building perl. If you
271 have the Sun C compilers, you will also have a parallel version of
272 make (dmake). This works fine to build perl, but can sometimes cause
273 problems when running 'make test' due to underspecified dependencies
274 between the different test harness files. The same problem can also
275 affect the building of some add-on modules, so in those cases either
276 specify '-m serial' on the dmake command line, or use
277 /usr/ccs/bin/make instead. If you wish to use GNU make, be sure that
278 the set-group-id bit is not set. If it is, then arrange your PATH so
279 that /usr/ccs/bin/make is before GNU make or else have the system
280 administrator disable the set-group-id bit on GNU make.
284 Solaris provides some BSD-compatibility functions in /usr/ucblib/libucb.a.
285 Perl will not build and run correctly if linked against -lucb since it
286 contains routines that are incompatible with the standard Solaris libc.
287 Normally this is not a problem since the solaris hints file prevents
288 Configure from even looking in /usr/ucblib for libraries, and also
289 explicitly omits -lucb.
291 =head2 Environment for Compiling perl on Solaris
295 Make sure your PATH includes the compiler (/opt/SUNWspro/bin/ if you're
296 using Sun's compiler) as well as /usr/ccs/bin/ to pick up the other
297 development tools (such as make, ar, as, and ld). Make sure your path
298 either doesn't include /usr/ucb or that it includes it after the
299 compiler and compiler tools and other standard Solaris directories.
300 You definitely don't want /usr/ucb/cc.
302 =head3 LD_LIBRARY_PATH
304 If you have the LD_LIBRARY_PATH environment variable set, be sure that
305 it does NOT include /lib or /usr/lib. If you will be building
306 extensions that call third-party shared libraries (e.g. Berkeley DB)
307 then make sure that your LD_LIBRARY_PATH environment variable includes
308 the directory with that library (e.g. /usr/local/lib).
310 If you get an error message
312 dlopen: stub interception failed
314 it is probably because your LD_LIBRARY_PATH environment variable
315 includes a directory which is a symlink to /usr/lib (such as /lib).
316 The reason this causes a problem is quite subtle. The file
317 libdl.so.1.0 actually *only* contains functions which generate 'stub
318 interception failed' errors! The runtime linker intercepts links to
319 "/usr/lib/libdl.so.1.0" and links in internal implementations of those
320 functions instead. [Thanks to Tim Bunce for this explanation.]
324 See the INSTALL file for general information regarding Configure.
325 Only Solaris-specific issues are discussed here. Usually, the
326 defaults should be fine.
328 =head2 64-bit perl on Solaris
330 See the INSTALL file for general information regarding 64-bit compiles.
331 In general, the defaults should be fine for most people.
333 By default, perl-5.6.0 (or later) is compiled as a 32-bit application
334 with largefile and long-long support.
336 =head3 General 32-bit vs. 64-bit issues
338 Solaris 7 and above will run in either 32 bit or 64 bit mode on SPARC
339 CPUs, via a reboot. You can build 64 bit apps whilst running 32 bit
340 mode and vice-versa. 32 bit apps will run under Solaris running in
341 either 32 or 64 bit mode. 64 bit apps require Solaris to be running
344 Existing 32 bit apps are properly known as LP32, i.e. Longs and
345 Pointers are 32 bit. 64-bit apps are more properly known as LP64.
346 The discriminating feature of a LP64 bit app is its ability to utilise a
347 64-bit address space. It is perfectly possible to have a LP32 bit app
348 that supports both 64-bit integers (long long) and largefiles (> 2GB),
349 and this is the default for perl-5.6.0.
351 For a more complete explanation of 64-bit issues, see the
352 "Solaris 64-bit Developer's Guide" at L<http://docs.sun.com/>
354 You can detect the OS mode using "isainfo -v", e.g.
356 $ isainfo -v # Ultra 30 in 64 bit mode
357 64-bit sparcv9 applications
358 32-bit sparc applications
360 By default, perl will be compiled as a 32-bit application. Unless
361 you want to allocate more than ~ 4GB of memory inside perl, or unless
362 you need more than 255 open file descriptors, you probably don't need
363 perl to be a 64-bit app.
365 =head3 Large File Support
367 For Solaris 2.6 and onwards, there are two different ways for 32-bit
368 applications to manipulate large files (files whose size is > 2GByte).
369 (A 64-bit application automatically has largefile support built in
372 First is the "transitional compilation environment", described in
373 lfcompile64(5). According to the man page,
375 The transitional compilation environment exports all the
376 explicit 64-bit functions (xxx64()) and types in addition to
377 all the regular functions (xxx()) and types. Both xxx() and
378 xxx64() functions are available to the program source. A
379 32-bit application must use the xxx64() functions in order
380 to access large files. See the lf64(5) manual page for a
381 complete listing of the 64-bit transitional interfaces.
383 The transitional compilation environment is obtained with the
384 following compiler and linker flags:
386 getconf LFS64_CFLAGS -D_LARGEFILE64_SOURCE
387 getconf LFS64_LDFLAG # nothing special needed
388 getconf LFS64_LIBS # nothing special needed
390 Second is the "large file compilation environment", described in
391 lfcompile(5). According to the man page,
393 Each interface named xxx() that needs to access 64-bit entities
394 to access large files maps to a xxx64() call in the
395 resulting binary. All relevant data types are defined to be
396 of correct size (for example, off_t has a typedef definition
397 for a 64-bit entity).
399 An application compiled in this environment is able to use
400 the xxx() source interfaces to access both large and small
401 files, rather than having to explicitly utilize the transitional
402 xxx64() interface calls to access large files.
404 Two exceptions are fseek() and ftell(). 32-bit applications should
405 use fseeko(3C) and ftello(3C). These will get automatically mapped
406 to fseeko64() and ftello64().
408 The large file compilation environment is obtained with
410 getconf LFS_CFLAGS -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64
411 getconf LFS_LDFLAGS # nothing special needed
412 getconf LFS_LIBS # nothing special needed
414 By default, perl uses the large file compilation environment and
415 relies on Solaris to do the underlying mapping of interfaces.
417 =head3 Building an LP64 perl
419 To compile a 64-bit application on an UltraSparc with a recent Sun Compiler,
420 you need to use the flag "-xarch=v9". getconf(1) will tell you this, e.g.
422 $ getconf -a | grep v9
423 XBS5_LP64_OFF64_CFLAGS: -xarch=v9
424 XBS5_LP64_OFF64_LDFLAGS: -xarch=v9
425 XBS5_LP64_OFF64_LINTFLAGS: -xarch=v9
426 XBS5_LPBIG_OFFBIG_CFLAGS: -xarch=v9
427 XBS5_LPBIG_OFFBIG_LDFLAGS: -xarch=v9
428 XBS5_LPBIG_OFFBIG_LINTFLAGS: -xarch=v9
429 _XBS5_LP64_OFF64_CFLAGS: -xarch=v9
430 _XBS5_LP64_OFF64_LDFLAGS: -xarch=v9
431 _XBS5_LP64_OFF64_LINTFLAGS: -xarch=v9
432 _XBS5_LPBIG_OFFBIG_CFLAGS: -xarch=v9
433 _XBS5_LPBIG_OFFBIG_LDFLAGS: -xarch=v9
434 _XBS5_LPBIG_OFFBIG_LINTFLAGS: -xarch=v9
436 This flag is supported in Sun WorkShop Compilers 5.0 and onwards
437 (now marketed under the name Forte) when used on Solaris 7 or later on
440 If you are using gcc, you would need to use -mcpu=v9 -m64 instead. This
441 option is not yet supported as of gcc 2.95.2; from install/SPECIFIC
444 GCC version 2.95 is not able to compile code correctly for sparc64
445 targets. Users of the Linux kernel, at least, can use the sparc32
446 program to start up a new shell invocation with an environment that
447 causes configure to recognize (via uname -a) the system as sparc-*-*
450 All this should be handled automatically by the hints file, if
455 As of 5.8.1, long doubles are working if you use the Sun compilers
456 (needed for additional math routines not included in libm).
458 =head2 Threads in perl on Solaris
460 It is possible to build a threaded version of perl on Solaris. The entire
461 perl thread implementation is still experimental, however, so beware.
463 =head2 Malloc Issues with perl on Solaris
465 Starting from perl 5.7.1 perl uses the Solaris malloc, since the perl
466 malloc breaks when dealing with more than 2GB of memory, and the Solaris
467 malloc also seems to be faster.
469 If you for some reason (such as binary backward compatibility) really
470 need to use perl's malloc, you can rebuild perl from the sources
471 and Configure the build with
473 $ sh Configure -Dusemymalloc
475 You should not use perl's malloc if you are building with gcc. There
476 are reports of core dumps, especially in the PDL module. The problem
477 appears to go away under -DDEBUGGING, so it has been difficult to
478 track down. Sun's compiler appears to be okay with or without perl's
479 malloc. [XXX further investigation is needed here.]
485 =item Dynamic Loading Problems With GNU as and GNU ld
487 If you have problems with dynamic loading using gcc on SunOS or
488 Solaris, and you are using GNU as and GNU ld, see the section
489 L</"GNU as and GNU ld"> above.
491 =item ld.so.1: ./perl: fatal: relocation error:
493 If you get this message on SunOS or Solaris, and you're using gcc,
494 it's probably the GNU as or GNU ld problem in the previous item
495 L</"GNU as and GNU ld">.
497 =item dlopen: stub interception failed
499 The primary cause of the 'dlopen: stub interception failed' message is
500 that the LD_LIBRARY_PATH environment variable includes a directory
501 which is a symlink to /usr/lib (such as /lib). See
502 L</"LD_LIBRARY_PATH"> above.
504 =item #error "No DATAMODEL_NATIVE specified"
506 This is a common error when trying to build perl on Solaris 2.6 with a
507 gcc installation from Solaris 2.5 or 2.5.1. The Solaris header files
508 changed, so you need to update your gcc installation. You can either
509 rerun the fixincludes script from gcc or take the opportunity to
510 update your gcc installation.
512 =item sh: ar: not found
514 This is a message from your shell telling you that the command 'ar'
515 was not found. You need to check your PATH environment variable to
516 make sure that it includes the directory with the 'ar' command. This
517 is a common problem on Solaris, where 'ar' is in the /usr/ccs/bin/
524 =head2 op/stat.t test 4 in Solaris
526 F<op/stat.t> test 4 may fail if you are on a tmpfs of some sort.
527 Building in /tmp sometimes shows this behavior. The
528 test suite detects if you are building in /tmp, but it may not be able
529 to catch all tmpfs situations.
531 =head2 nss_delete core dump from op/pwent or op/grent
533 See L<perlhpux/"nss_delete core dump from op/pwent or op/grent">.
535 =head1 CROSS-COMPILATION
537 Nothing too unusual here. You can easily do this if you have a
538 cross-compiler available; A usual Configure invocation when targetting a
539 Solaris x86 looks something like this:
541 sh ./Configure -des -Dusecrosscompile \
542 -Dcc=i386-pc-solaris2.11-gcc \
544 -Alddlflags=" -Wl,-z,notext" \
545 -Dtargethost=... # The usual cross-compilation options
547 The lddlflags addition is the only abnormal bit.
549 =head1 PREBUILT BINARIES OF PERL FOR SOLARIS
551 You can pick up prebuilt binaries for Solaris from
552 L<http://www.sunfreeware.com/>, L<http://www.blastwave.org>,
553 ActiveState L<http://www.activestate.com/>, and
554 L<http://www.perl.com/> under the Binaries list at the top of the
555 page. There are probably other sources as well. Please note that
556 these sites are under the control of their respective owners, not the
559 =head1 RUNTIME ISSUES FOR PERL ON SOLARIS
561 =head2 Limits on Numbers of Open Files on Solaris
563 The stdio(3C) manpage notes that for LP32 applications, only 255
564 files may be opened using fopen(), and only file descriptors 0
565 through 255 can be used in a stream. Since perl calls open() and
566 then fdopen(3C) with the resulting file descriptor, perl is limited
567 to 255 simultaneous open files, even if sysopen() is used. If this
568 proves to be an insurmountable problem, you can compile perl as a
569 LP64 application, see L</Building an LP64 perl> for details. Note
570 also that the default resource limit for open file descriptors on
571 Solaris is 255, so you will have to modify your ulimit or rctl
572 (Solaris 9 onwards) appropriately.
574 =head1 SOLARIS-SPECIFIC MODULES
576 See the modules under the Solaris:: and Sun::Solaris namespaces on CPAN,
577 see L<http://www.cpan.org/modules/by-module/Solaris/> and
578 L<http://www.cpan.org/modules/by-module/Sun/>.
580 =head1 SOLARIS-SPECIFIC PROBLEMS WITH MODULES
582 =head2 Proc::ProcessTable on Solaris
584 Proc::ProcessTable does not compile on Solaris with perl5.6.0 and higher
585 if you have LARGEFILES defined. Since largefile support is the
586 default in 5.6.0 and later, you have to take special steps to use this
589 The problem is that various structures visible via procfs use off_t,
590 and if you compile with largefile support these change from 32 bits to
591 64 bits. Thus what you get back from procfs doesn't match up with
592 the structures in perl, resulting in garbage. See proc(4) for further
595 A fix for Proc::ProcessTable is to edit Makefile to
596 explicitly remove the largefile flags from the ones MakeMaker picks up
597 from Config.pm. This will result in Proc::ProcessTable being built
598 under the correct environment. Everything should then be OK as long as
599 Proc::ProcessTable doesn't try to share off_t's with the rest of perl,
600 or if it does they should be explicitly specified as off64_t.
602 =head2 BSD::Resource on Solaris
604 BSD::Resource versions earlier than 1.09 do not compile on Solaris
605 with perl 5.6.0 and higher, for the same reasons as Proc::ProcessTable.
606 BSD::Resource versions starting from 1.09 have a workaround for the problem.
608 =head2 Net::SSLeay on Solaris
610 Net::SSLeay requires a /dev/urandom to be present. This device is
611 available from Solaris 9 onwards. For earlier Solaris versions you
612 can either get the package SUNWski (packaged with several Sun
613 software products, for example the Sun WebServer, which is part of
614 the Solaris Server Intranet Extension, or the Sun Directory Services,
615 part of Solaris for ISPs) or download the ANDIrand package from
616 L<http://www.cosy.sbg.ac.at/~andi/>. If you use SUNWski, make a
617 symbolic link /dev/urandom pointing to /dev/random. For more details,
618 see Document ID27606 entitled "Differing /dev/random support requirements
619 within Solaris[TM] Operating Environments", available at
620 L<http://sunsolve.sun.com> .
622 It may be possible to use the Entropy Gathering Daemon (written in
623 Perl!), available from L<http://www.lothar.com/tech/crypto/>.
627 In SunOS 4.x you most probably want to use the SunOS ld, /usr/bin/ld,
628 since the more recent versions of GNU ld (like 2.13) do not seem to
629 work for building Perl anymore. When linking the extensions, the
630 GNU ld gets very unhappy and spews a lot of errors like this
632 ... relocation truncated to fit: BASE13 ...
634 and dies. Therefore the SunOS 4.1 hints file explicitly sets the
635 ld to be F</usr/bin/ld>.
637 As of Perl 5.8.1 the dynamic loading of libraries (DynaLoader, XSLoader)
638 also seems to have become broken in in SunOS 4.x. Therefore the default
639 is to build Perl statically.
641 Running the test suite in SunOS 4.1 is a bit tricky since the
642 F<dist/Tie-File/t/09_gen_rs.t> test hangs (subtest #51, FWIW) for some
643 unknown reason. Just stop the test and kill that particular Perl
646 There are various other failures, that as of SunOS 4.1.4 and gcc 3.2.2
647 look a lot like gcc bugs. Many of the failures happen in the Encode
648 tests, where for example when the test expects "0" you get "0"
649 which should after a little squinting look very odd indeed.
650 Another example is earlier in F<t/run/fresh_perl> where chr(0xff) is
651 expected but the test fails because the result is chr(0xff). Exactly.
653 This is the "make test" result from the said combination:
655 Failed 27 test scripts out of 745, 96.38% okay.
657 Running the C<harness> is painful because of the many failing
658 Unicode-related tests will output megabytes of failure messages,
659 but if one patiently waits, one gets these results:
661 Failed Test Stat Wstat Total Fail Failed List of Failed
662 -----------------------------------------------------------------------------
664 ../ext/Encode/t/at-cn.t 4 1024 29 4 13.79% 14-17
665 ../ext/Encode/t/at-tw.t 10 2560 17 10 58.82% 2 4 6 8 10 12
667 ../ext/Encode/t/enc_data.t 29 7424 ?? ?? % ??
668 ../ext/Encode/t/enc_eucjp.t 29 7424 ?? ?? % ??
669 ../ext/Encode/t/enc_module.t 29 7424 ?? ?? % ??
670 ../ext/Encode/t/encoding.t 29 7424 ?? ?? % ??
671 ../ext/Encode/t/grow.t 12 3072 24 12 50.00% 2 4 6 8 10 12 14
673 Failed Test Stat Wstat Total Fail Failed List of Failed
674 ------------------------------------------------------------------------------
675 ../ext/Encode/t/guess.t 255 65280 29 40 137.93% 10-29
676 ../ext/Encode/t/jperl.t 29 7424 15 30 200.00% 1-15
677 ../ext/Encode/t/mime-header.t 2 512 10 2 20.00% 2-3
678 ../ext/Encode/t/perlio.t 22 5632 38 22 57.89% 1-4 9-16 19-20
680 ../ext/List/Util/t/shuffle.t 0 139 ?? ?? % ??
681 ../ext/PerlIO/t/encoding.t 14 1 7.14% 11
682 ../ext/PerlIO/t/fallback.t 9 2 22.22% 3 5
683 ../ext/Socket/t/socketpair.t 0 2 45 70 155.56% 11-45
684 ../lib/CPAN/t/vcmp.t 30 1 3.33% 25
685 ../lib/Tie/File/t/09_gen_rs.t 0 15 ?? ?? % ??
686 ../lib/Unicode/Collate/t/test.t 199 30 15.08% 7 26-27 71-75
691 ../lib/sort.t 0 139 119 26 21.85% 107-119
692 op/alarm.t 4 1 25.00% 4
693 op/utfhash.t 97 1 1.03% 31
694 run/fresh_perl.t 91 1 1.10% 32
695 uni/tr_7jis.t ?? ?? % ??
696 uni/tr_eucjp.t 29 7424 6 12 200.00% 1-6
697 uni/tr_sjis.t 29 7424 6 12 200.00% 1-6
698 56 tests and 467 subtests skipped.
699 Failed 27/811 test scripts, 96.67% okay. 1383/75399 subtests failed,
702 The alarm() test failure is caused by system() apparently blocking
703 alarm(). That is probably a libc bug, and given that SunOS 4.x
704 has been end-of-lifed years ago, don't hold your breath for a fix.
705 In addition to that, don't try anything too Unicode-y, especially
706 with Encode, and you should be fine in SunOS 4.x.
710 The original was written by Andy Dougherty F<doughera@lafayette.edu>
711 drawing heavily on advice from Alan Burlison, Nick Ing-Simmons, Tim Bunce,
712 and many other Solaris users over the years.
714 Please report any errors, updates, or suggestions to
715 L<https://github.com/Perl/perl5/issues>.