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