Cari di Perl 
     Perl User Manual
Daftar Isi ☛
(Sebelumnya) Perl version 5 for RISC OSPerl version 5 on Symbian OS (Berikutnya)
Platform Specific

Perl version 5 on Solaris systems

Daftar Isi

NAME

perlsolaris - Perl version 5 on Solaris systems

DESCRIPTION

This document describes various features of Sun's Solaris operating systemthat will affect how Perl version 5 (hereafter just perl) iscompiled and/or runs. Some issues relating to the older SunOS 4.x arealso discussed, though they may be out of date.

For the most part, everything should just work.

Starting with Solaris 8, perl5.00503 (or higher) is supplied with theoperating system, so you might not even need to build a newer versionof perl at all. The Sun-supplied version is installed in /usr/perl5with /usr/bin/perl pointing to /usr/perl5/bin/perl. Do not disturbthat installation unless you really know what you are doing. If youremove the perl supplied with the OS, you will render some bits ofyour system inoperable. If you wish to install a newer version of perl,install it under a different prefix from /usr/perl5. Common prefixesto use are /usr/local and /opt/perl.

You may wish to put your version of perl in the PATH of all users bychanging the link /usr/bin/perl. This is probably OK, as most perlscripts shipped with Solaris use an explicit path. (There are a fewexceptions, such as /usr/bin/rpm2cpio and /etc/rcm/scripts/README, butthese are also sufficiently generic that the actual version of perlprobably doesn't matter too much.)

Solaris ships with a range of Solaris-specific modules. If you chooseto install your own version of perl you will find the source of many ofthese modules is available on CPAN under the Sun::Solaris:: namespace.

Solaris may include two versions of perl, e.g. Solaris 9 includesboth 5.005_03 and 5.6.1. This is to provide stability across Solarisreleases, in cases where a later perl version has incompatibilitieswith the version included in the preceding Solaris release. Thedefault perl version will always be the most recent, and in generalthe old version will only be retained for one Solaris release. Notealso that the default perl will NOT be configured to search for modulesin the older version, again due to compatibility/stability concerns.As a consequence if you upgrade Solaris, you will have torebuild/reinstall any additional CPAN modules that you installed forthe previous Solaris version. See the CPAN manpage under 'autobundle'for a quick way of doing this.

As an interim measure, you may either change the #! line of yourscripts to specifically refer to the old perl version, e.g. onSolaris 9 use #!/usr/perl5/5.00503/bin/perl to use the perl versionthat was the default for Solaris 8, or if you have a large number ofscripts it may be more convenient to make the old version of perl thedefault on your system. You can do this by changing the appropriatesymlinks under /usr/perl5 as follows (example for Solaris 9):

  1.  # cd /usr/perl5
    2.  
  2.  # rm bin man pod
    3.  
  3.  # ln -s ./5.00503/bin
    4.  
  4.  # ln -s ./5.00503/man
    5.  
  5.  # ln -s ./5.00503/lib/pod
    6.  
  6.  # rm /usr/bin/perl
    7.  
  7.  # ln -s ../perl5/5.00503/bin/perl /usr/bin/perl
    8.

In both cases this should only be considered to be a temporarymeasure - you should upgrade to the later version of perl as soon asis practicable.

Note also that the perl command-line utilities (e.g. perldoc) and anythat are added by modules that you install will be under/usr/perl5/bin, so that directory should be added to your PATH.

Solaris Version Numbers.

For consistency with common usage, perl's Configure script performssome minor manipulations on the operating system name and versionnumber as reported by uname. Here's a partial translation table:

  1.   Sun:  perl's Configure:
    2.  
  2.  uname uname -r   Name   osname osvers
    3.  
  3.  SunOS 4.1.3 Solaris 1.1 sunos  4.1.3
    4.  
  4.  SunOS 5.6   Solaris 2.6 solaris 2.6
    5.  
  5.  SunOS 5.8   Solaris 8   solaris 2.8
    6.  
  6.  SunOS 5.9   Solaris 9   solaris 2.9
    7.  
  7.  SunOS 5.10  Solaris 10  solaris 2.10
    8.

The complete table can be found in the Sun Managers' FAQftp://ftp.cs.toronto.edu/pub/jdd/sunmanagers/faq under"9.1) Which Sun models run which versions of SunOS?".

RESOURCES

There are many, many sources for Solaris information. A few of theimportant ones for perl:

SETTING UP

File Extraction Problems on Solaris.

Be sure to use a tar program compiled under Solaris (not SunOS 4.x)to extract the perl-5.x.x.tar.gz file. Do not use GNU tar compiledfor SunOS4 on Solaris. (GNU tar compiled for Solaris should be fine.)When you run SunOS4 binaries on Solaris, the run-time system magicallyalters pathnames matching m#lib/locale# so that when tar tries to createlib/locale.pm, a file named lib/oldlocale.pm gets created instead.If you found this advice too late and used a SunOS4-compiled taranyway, you must find the incorrectly renamed file and move it backto lib/locale.pm.

Compiler and Related Tools on Solaris.

You must use an ANSI C compiler to build perl. Perl can be compiledwith either Sun's add-on C compiler or with gcc. The C compiler thatshipped with SunOS4 will not do.

Include /usr/ccs/bin/ in your PATH.

Several tools needed to build perl are located in /usr/ccs/bin/: ar,as, ld, and make. Make sure that /usr/ccs/bin/ is in your PATH.

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):

for tools (sccs, lex, yacc, make, nm, truss, ld, as): SUNWbtool,SUNWsprot, SUNWtoo

for libraries & headers: SUNWhea, SUNWarc, SUNWlibm, SUNWlibms, SUNWdfbh,SUNWcg6h, SUNWxwinc

Additionaly, on Solaris 8 and 9 you also need:

for 64 bit development: SUNWarcx, SUNWbtoox, SUNWdplx, SUNWscpux,SUNWsprox, SUNWtoox, SUNWlmsx, SUNWlmx, SUNWlibCx

And only on Solaris 8 you also need:

for libraries & headers: SUNWolinc

If you are in doubt which package contains a file you are missing,try to find an installation that has that file. Then do a

  1.  $ grep /my/missing/file /var/sadm/install/contents
    2.

This will display a line like this:

/usr/include/sys/errno.h f none 0644 root bin 7471 37605 956241356 SUNWhea

The last item listed (SUNWhea in this example) is the package you need.

Avoid /usr/ucb/cc.

You don't need to have /usr/ucb/ in your PATH to build perl. If youwant /usr/ucb/ in your PATH anyway, make sure that /usr/ucb/ is NOTin your PATH before the directory containing the right C compiler.

Sun's C Compiler

If you use Sun's C compiler, make sure the correct directory(usually /opt/SUNWspro/bin/) is in your PATH (before /usr/ucb/).

GCC

If you use gcc, make sure your installation is recent and complete.perl versions since 5.6.0 build fine with gcc > 2.8.1 on Solaris >=2.6.

You must Configure perl with

  1.  $ sh Configure -Dcc=gcc
    2.

If you don't, you may experience strange build errors.

If you have updated your Solaris version, you may also have to updateyour gcc. For example, if you are running Solaris 2.6 and your gcc isinstalled under /usr/local, check in /usr/local/lib/gcc-lib and makesure you have the appropriate directory, sparc-sun-solaris2.6/ ori386-pc-solaris2.6/. If gcc's directory is for a different version ofSolaris than you are running, then you will need to rebuild gcc foryour new version of Solaris.

You can get a precompiled version of gcc fromhttp://www.sunfreeware.com/ or http://www.blastwave.org/. Makesure you pick up the package for your Solaris release.

If you wish to use gcc to build add-on modules for use with the perlshipped with Solaris, you should use the Solaris::PerlGcc modulewhich is available from CPAN. The perl shipped with Solarisis configured and built with the Sun compilers, and the compilerconfiguration information stored in Config.pm is therefore onlyrelevant to the Sun compilers. The Solaris:PerlGcc module contains areplacement Config.pm that is correct for gcc - see the module fordetails.

GNU as and GNU ld

The following information applies to gcc version 2. Volunteers toupdate it as appropriately for gcc version 3 would be appreciated.

The versions of as and ld supplied with Solaris work fine for buildingperl. There is normally no need to install the GNU versions tocompile perl.

If you decide to ignore this advice and use the GNU versions anyway,then be sure that they are relatively recent. Versions newer than 2.7are apparently new enough. Older versions may have trouble withdynamic loading.

If you wish to use GNU ld, then you need to pass it the -Wl,-E flag.The hints/solaris_2.sh file tries to do this automatically by settingthe following Configure variables:

  1.  ccdlflags="$ccdlflags -Wl,-E"
    2.  
  2.  lddlflags="$lddlflags -Wl,-E -G"
    3.

However, over the years, changes in gcc, GNU ld, and Solaris ld have madeit difficult to automatically detect which ld ultimately gets called.You may have to manually edit config.sh and add the -Wl,-E flagsyourself, or else run Configure interactively and add the flags at theappropriate prompts.

If your gcc is configured to use GNU as and ld but you want to use theSolaris ones instead to build perl, then you'll need to add-B/usr/ccs/bin/ to the gcc command line. One convenient way to dothat is with

  1.  $ sh Configure -Dcc='gcc -B/usr/ccs/bin/'
    2.

Note that the trailing slash is required. This will result in someharmless warnings as Configure is run:

  1.  gcc: file path prefix `/usr/ccs/bin/' never used
    2.

These messages may safely be ignored.(Note that for a SunOS4 system, you must use -B/bin/ instead.)

Alternatively, you can use the GCC_EXEC_PREFIX environment variable toensure that Sun's as and ld are used. Consult your gcc documentationfor further information on the -B option and the GCC_EXEC_PREFIX variable.

Sun and GNU make

The make under /usr/ccs/bin works fine for building perl. If youhave the Sun C compilers, you will also have a parallel version ofmake (dmake). This works fine to build perl, but can sometimes causeproblems when running 'make test' due to underspecified dependenciesbetween the different test harness files. The same problem can alsoaffect the building of some add-on modules, so in those cases eitherspecify '-m serial' on the dmake command line, or use/usr/ccs/bin/make instead. If you wish to use GNU make, be sure thatthe set-group-id bit is not set. If it is, then arrange your PATH sothat /usr/ccs/bin/make is before GNU make or else have the systemadministrator disable the set-group-id bit on GNU make.

Avoid libucb.

Solaris provides some BSD-compatibility functions in /usr/ucblib/libucb.a.Perl will not build and run correctly if linked against -lucb since itcontains routines that are incompatible with the standard Solaris libc.Normally this is not a problem since the solaris hints file preventsConfigure from even looking in /usr/ucblib for libraries, and alsoexplicitly omits -lucb.

Environment for Compiling perl on Solaris

PATH

Make sure your PATH includes the compiler (/opt/SUNWspro/bin/ if you'reusing Sun's compiler) as well as /usr/ccs/bin/ to pick up the otherdevelopment tools (such as make, ar, as, and ld). Make sure your patheither doesn't include /usr/ucb or that it includes it after thecompiler and compiler tools and other standard Solaris directories.You definitely don't want /usr/ucb/cc.

LD_LIBRARY_PATH

If you have the LD_LIBRARY_PATH environment variable set, be sure thatit does NOT include /lib or /usr/lib. If you will be buildingextensions that call third-party shared libraries (e.g. Berkeley DB)then make sure that your LD_LIBRARY_PATH environment variable includesthe directory with that library (e.g. /usr/local/lib).

If you get an error message

  1.  dlopen: stub interception failed
    2.

it is probably because your LD_LIBRARY_PATH environment variableincludes a directory which is a symlink to /usr/lib (such as /lib).The reason this causes a problem is quite subtle. The filelibdl.so.1.0 actually *only* contains functions which generate 'stubinterception failed' errors! The runtime linker intercepts links to"/usr/lib/libdl.so.1.0" and links in internal implementations of thosefunctions instead. [Thanks to Tim Bunce for this explanation.]

RUN CONFIGURE.

See the INSTALL file for general information regarding Configure.Only Solaris-specific issues are discussed here. Usually, thedefaults should be fine.

64-bit perl on Solaris.

See the INSTALL file for general information regarding 64-bit compiles.In general, the defaults should be fine for most people.

By default, perl-5.6.0 (or later) is compiled as a 32-bit applicationwith largefile and long-long support.

General 32-bit vs. 64-bit issues.

Solaris 7 and above will run in either 32 bit or 64 bit mode on SPARCCPUs, via a reboot. You can build 64 bit apps whilst running 32 bitmode and vice-versa. 32 bit apps will run under Solaris running ineither 32 or 64 bit mode. 64 bit apps require Solaris to be running64 bit mode.

Existing 32 bit apps are properly known as LP32, i.e. Longs andPointers are 32 bit. 64-bit apps are more properly known as LP64.The discriminating feature of a LP64 bit app is its ability to utilise a64-bit address space. It is perfectly possible to have a LP32 bit appthat supports both 64-bit integers (long long) and largefiles (> 2GB),and this is the default for perl-5.6.0.

For a more complete explanation of 64-bit issues, see the"Solaris 64-bit Developer's Guide" at http://docs.sun.com/

You can detect the OS mode using "isainfo -v", e.g.

  1.  $ isainfo -v   # Ultra 30 in 64 bit mode
    2.  
  2.  64-bit sparcv9 applications
    3.  
  3.  32-bit sparc applications
    4.

By default, perl will be compiled as a 32-bit application. Unlessyou want to allocate more than ~ 4GB of memory inside perl, or unlessyou need more than 255 open file descriptors, you probably don't needperl to be a 64-bit app.

Large File Support

For Solaris 2.6 and onwards, there are two different ways for 32-bitapplications to manipulate large files (files whose size is > 2GByte).(A 64-bit application automatically has largefile support built inby default.)

First is the "transitional compilation environment", described inlfcompile64(5). According to the man page,

  1.  The transitional compilation  environment  exports  all  the
    2.  
  2.  explicit 64-bit functions (xxx64()) and types in addition to
    3.  
  3.  all the regular functions (xxx()) and types. Both xxx()  and
    4.  
  4.  xxx64()  functions  are  available to the program source.  A
    5.  
  5.  32-bit application must use the xxx64() functions in  order
    6.  
  6.  to  access  large  files.  See the lf64(5) manual page for a
    7.  
  7.  complete listing of the 64-bit transitional interfaces.
    8.

The transitional compilation environment is obtained with thefollowing compiler and linker flags:

  1.  getconf LFS64_CFLAGS -D_LARGEFILE64_SOURCE
    2.  
  2.  getconf LFS64_LDFLAG # nothing special needed
    3.  
  3.  getconf LFS64_LIBS  # nothing special needed
    4.

Second is the "large file compilation environment", described inlfcompile(5). According to the man page,

  1.  Each interface named xxx() that needs to access 64-bit entities
    2.  
  2.  to  access  large  files maps to a xxx64() call in the
    3.  
  3.  resulting binary. All relevant data types are defined to  be
    4.  
  4.  of correct size (for example, off_t has a typedef definition
    5.  
  5.  for a 64-bit entity).
    6.  
  6.  
  7.  An application compiled in this environment is able  to  use
    8.  
  8.  the  xxx()  source interfaces to access both large and small
    9.  
  9.  files, rather than having to explicitly utilize the  transitional
    10.  
  10.  xxx64()  interface  calls to access large files.
    11.

Two exceptions are fseek() and ftell(). 32-bit applications shoulduse fseeko(3C) and ftello(3C). These will get automatically mappedto fseeko64() and ftello64().

The large file compilation environment is obtained with

  1.  getconf LFS_CFLAGS  -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64
    2.  
  2.  getconf LFS_LDFLAGS # nothing special needed
    3.  
  3.  getconf LFS_LIBS # nothing special needed
    4.

By default, perl uses the large file compilation environment andrelies on Solaris to do the underlying mapping of interfaces.

Building an LP64 perl

To compile a 64-bit application on an UltraSparc with a recent Sun Compiler,you need to use the flag "-xarch=v9". getconf(1) will tell you this, e.g.

  1.  $ getconf -a | grep v9
    2.  
  2.  XBS5_LP64_OFF64_CFLAGS: -xarch=v9
    3.  
  3.  XBS5_LP64_OFF64_LDFLAGS: -xarch=v9
    4.  
  4.  XBS5_LP64_OFF64_LINTFLAGS:  -xarch=v9
    5.  
  5.  XBS5_LPBIG_OFFBIG_CFLAGS:   -xarch=v9
    6.  
  6.  XBS5_LPBIG_OFFBIG_LDFLAGS:  -xarch=v9
    7.  
  7.  XBS5_LPBIG_OFFBIG_LINTFLAGS: -xarch=v9
    8.  
  8.  _XBS5_LP64_OFF64_CFLAGS: -xarch=v9
    9.  
  9.  _XBS5_LP64_OFF64_LDFLAGS:   -xarch=v9
    10.  
  10.  _XBS5_LP64_OFF64_LINTFLAGS: -xarch=v9
    11.  
  11.  _XBS5_LPBIG_OFFBIG_CFLAGS:  -xarch=v9
    12.  
  12.  _XBS5_LPBIG_OFFBIG_LDFLAGS: -xarch=v9
    13.  
  13.  _XBS5_LPBIG_OFFBIG_LINTFLAGS:   -xarch=v9
    14.

This flag is supported in Sun WorkShop Compilers 5.0 and onwards(now marketed under the name Forte) when used on Solaris 7 or later onUltraSparc systems.

If you are using gcc, you would need to use -mcpu=v9 -m64 instead. Thisoption is not yet supported as of gcc 2.95.2; from install/SPECIFICin that release:

  1.  GCC version 2.95 is not able to compile code correctly for sparc64
    2.  
  2.  targets. Users of the Linux kernel, at least, can use the sparc32
    3.  
  3.  program to start up a new shell invocation with an environment that
    4.  
  4.  causes configure to recognize (via uname -a) the system as sparc-*-*
    5.  
  5.  instead.
    6.

All this should be handled automatically by the hints file, ifrequested.

Long Doubles.

As of 5.8.1, long doubles are working if you use the Sun compilers(needed for additional math routines not included in libm).

Threads in perl on Solaris.

It is possible to build a threaded version of perl on Solaris. The entireperl thread implementation is still experimental, however, so beware.

Malloc Issues with perl on Solaris.

Starting from perl 5.7.1 perl uses the Solaris malloc, since the perlmalloc breaks when dealing with more than 2GB of memory, and the Solarismalloc also seems to be faster.

If you for some reason (such as binary backward compatibility) reallyneed to use perl's malloc, you can rebuild perl from the sourcesand Configure the build with

  1.  $ sh Configure -Dusemymalloc
    2.

You should not use perl's malloc if you are building with gcc. Thereare reports of core dumps, especially in the PDL module. The problemappears to go away under -DDEBUGGING, so it has been difficult totrack down. Sun's compiler appears to be okay with or without perl'smalloc. [XXX further investigation is needed here.]

MAKE PROBLEMS.

  • Dynamic Loading Problems With GNU as and GNU ld

    If you have problems with dynamic loading using gcc on SunOS orSolaris, and you are using GNU as and GNU ld, see the sectionGNU as and GNU ld above.

  • ld.so.1: ./perl: fatal: relocation error:

    If you get this message on SunOS or Solaris, and you're using gcc,it's probably the GNU as or GNU ld problem in the previous itemGNU as and GNU ld.

  • dlopen: stub interception failed

    The primary cause of the 'dlopen: stub interception failed' message isthat the LD_LIBRARY_PATH environment variable includes a directorywhich is a symlink to /usr/lib (such as /lib). SeeLD_LIBRARY_PATH above.

  • #error "No DATAMODEL_NATIVE specified"

    This is a common error when trying to build perl on Solaris 2.6 with agcc installation from Solaris 2.5 or 2.5.1. The Solaris header fileschanged, so you need to update your gcc installation. You can eitherrerun the fixincludes script from gcc or take the opportunity toupdate your gcc installation.

  • sh: ar: not found

    This is a message from your shell telling you that the command 'ar'was not found. You need to check your PATH environment variable tomake sure that it includes the directory with the 'ar' command. Thisis a common problem on Solaris, where 'ar' is in the /usr/ccs/bin/directory.

MAKE TEST

op/stat.t test 4 in Solaris

op/stat.t test 4 may fail if you are on a tmpfs of some sort.Building in /tmp sometimes shows this behavior. Thetest suite detects if you are building in /tmp, but it may not be ableto catch all tmpfs situations.

nss_delete core dump from op/pwent or op/grent

See nss_delete core dump from op/pwent or op/grent in perlhpux.

PREBUILT BINARIES OF PERL FOR SOLARIS.

You can pick up prebuilt binaries for Solaris fromhttp://www.sunfreeware.com/, http://www.blastwave.org,ActiveState http://www.activestate.com/, andhttp://www.perl.com/ under the Binaries list at the top of thepage. There are probably other sources as well. Please note thatthese sites are under the control of their respective owners, not theperl developers.

RUNTIME ISSUES FOR PERL ON SOLARIS.

Limits on Numbers of Open Files on Solaris.

The stdio(3C) manpage notes that for LP32 applications, only 255files may be opened using fopen(), and only file descriptors 0through 255 can be used in a stream. Since perl calls open() andthen fdopen(3C) with the resulting file descriptor, perl is limitedto 255 simultaneous open files, even if sysopen() is used. If thisproves to be an insurmountable problem, you can compile perl as aLP64 application, see Building an LP64 perl for details. Notealso that the default resource limit for open file descriptors onSolaris is 255, so you will have to modify your ulimit or rctl(Solaris 9 onwards) appropriately.

SOLARIS-SPECIFIC MODULES.

See the modules under the Solaris:: and Sun::Solaris namespaces on CPAN,see http://www.cpan.org/modules/by-module/Solaris/ andhttp://www.cpan.org/modules/by-module/Sun/.

SOLARIS-SPECIFIC PROBLEMS WITH MODULES.

Proc::ProcessTable on Solaris

Proc::ProcessTable does not compile on Solaris with perl5.6.0 and higherif you have LARGEFILES defined. Since largefile support is thedefault in 5.6.0 and later, you have to take special steps to use thismodule.

The problem is that various structures visible via procfs use off_t,and if you compile with largefile support these change from 32 bits to64 bits. Thus what you get back from procfs doesn't match up withthe structures in perl, resulting in garbage. See proc(4) for furtherdiscussion.

A fix for Proc::ProcessTable is to edit Makefile toexplicitly remove the largefile flags from the ones MakeMaker picks upfrom Config.pm. This will result in Proc::ProcessTable being builtunder the correct environment. Everything should then be OK as long asProc::ProcessTable doesn't try to share off_t's with the rest of perl,or if it does they should be explicitly specified as off64_t.

BSD::Resource on Solaris

BSD::Resource versions earlier than 1.09 do not compile on Solariswith perl 5.6.0 and higher, for the same reasons as Proc::ProcessTable.BSD::Resource versions starting from 1.09 have a workaround for the problem.

Net::SSLeay on Solaris

Net::SSLeay requires a /dev/urandom to be present. This device isavailable from Solaris 9 onwards. For earlier Solaris versions youcan either get the package SUNWski (packaged with several Sunsoftware products, for example the Sun WebServer, which is part ofthe Solaris Server Intranet Extension, or the Sun Directory Services,part of Solaris for ISPs) or download the ANDIrand package fromhttp://www.cosy.sbg.ac.at/~andi/. If you use SUNWski, make asymbolic link /dev/urandom pointing to /dev/random. For more details,see Document ID27606 entitled "Differing /dev/random support requirementswithin Solaris[TM] Operating Environments", available athttp://sunsolve.sun.com .

It may be possible to use the Entropy Gathering Daemon (written inPerl!), available from http://www.lothar.com/tech/crypto/.

SunOS 4.x

In SunOS 4.x you most probably want to use the SunOS ld, /usr/bin/ld,since the more recent versions of GNU ld (like 2.13) do not seem towork for building Perl anymore. When linking the extensions, theGNU ld gets very unhappy and spews a lot of errors like this

  1.   ... relocation truncated to fit: BASE13 ...
    2.

and dies. Therefore the SunOS 4.1 hints file explicitly sets theld to be /usr/bin/ld.

As of Perl 5.8.1 the dynamic loading of libraries (DynaLoader, XSLoader)also seems to have become broken in in SunOS 4.x. Therefore the defaultis to build Perl statically.

Running the test suite in SunOS 4.1 is a bit tricky since thelib/Tie/File/t/09_gen_rs test hangs (subtest #51, FWIW) for someunknown reason. Just stop the test and kill that particular Perlprocess.

There are various other failures, that as of SunOS 4.1.4 and gcc 3.2.2look a lot like gcc bugs. Many of the failures happen in the Encodetests, where for example when the test expects "0" you get "0"which should after a little squinting look very odd indeed.Another example is earlier in t/run/fresh_perl where chr(0xff) isexpected but the test fails because the result is chr(0xff). Exactly.

This is the "make test" result from the said combination:

  1.   Failed 27 test scripts out of 745, 96.38% okay.
    2.

Running the harness is painful because of the many failingUnicode-related tests will output megabytes of failure messages,but if one patiently waits, one gets these results:

  1.  Failed Test Stat Wstat Total Fail  Failed  List of Failed
    2.  
  2.  -----------------------------------------------------------------------------
    3.  
  3.  ...
    4.  
  4.  ../ext/Encode/t/at-cn.t 4  1024 29 4  13.79%  14-17
    5.  
  5.  ../ext/Encode/t/at-tw.t   10  2560 17   10  58.82%  2 4 6 8 10 12
    6.  
  6.  14-17
    7.  
  7.  ../ext/Encode/t/enc_data.t 29  7424 ??   ??   %  ??
    8.  
  8.  ../ext/Encode/t/enc_eucjp.t   29  7424 ??   ??   %  ??
    9.  
  9.  ../ext/Encode/t/enc_module.t  29  7424 ??   ??   %  ??
    10.  
  10.  ../ext/Encode/t/encoding.t 29  7424 ??   ??   %  ??
    11.  
  11.  ../ext/Encode/t/grow.t 12  3072 24   12  50.00%  2 4 6 8 10 12 14
    12.  
  12.  16 18 20 22 24
    13.  
  13.   Failed Test Stat Wstat Total Fail  Failed  List of Failed
    14.  
  14.  ------------------------------------------------------------------------------
    15.  
  15.  ../ext/Encode/t/guess.t  255 65280 29   40 137.93%  10-29
    16.  
  16.  ../ext/Encode/t/jperl.t   29  7424 15   30 200.00%  1-15
    17.  
  17.  ../ext/Encode/t/mime-header.t  2   512 10 2  20.00%  2-3
    18.  
  18.  ../ext/Encode/t/perlio.t  22  5632 38   22  57.89%  1-4 9-16 19-20
    19.  
  19.  23-24 27-32
    20.  
  20.  ../ext/List/Util/t/shuffle.t   0   139 ??   ??   %  ??
    21.  
  21.  ../ext/PerlIO/t/encoding.t 14 1   7.14%  11
    22.  
  22.  ../ext/PerlIO/t/fallback.t 9 2  22.22%  3 5
    23.  
  23.  ../ext/Socket/t/socketpair.t   0 2 45   70 155.56%  11-45
    24.  
  24.  ../lib/CPAN/t/vcmp.t  30 1   3.33%  25
    25.  
  25.  ../lib/Tie/File/t/09_gen_rs.t  0 15 ??   ??   %  ??
    26.  
  26.  ../lib/Unicode/Collate/t/test.t  199   30  15.08%  7 26-27 71-75
    27.  
  27.  81-88 95 101
    28.  
  28.  103-104 106 108-
    29.  
  29.  109 122 124 161
    30.  
  30.  169-172
    31.  
  31.  ../lib/sort.t  0   139   119   26  21.85%  107-119
    32.  
  32.  op/alarm.t 4 1  25.00%  4
    33.  
  33.  op/utfhash.t  97 1   1.03%  31
    34.  
  34.  run/fresh_perl.t  91 1   1.10%  32
    35.  
  35.  uni/tr_7jis.t ??   ??   %  ??
    36.  
  36.  uni/tr_eucjp.t 29  7424 6   12 200.00%  1-6
    37.  
  37.  uni/tr_sjis.t 29  7424 6   12 200.00%  1-6
    38.  
  38.  56 tests and 467 subtests skipped.
    39.  
  39.  Failed 27/811 test scripts, 96.67% okay. 1383/75399 subtests failed, 98.17% okay.
    40.

The alarm() test failure is caused by system() apparently blockingalarm(). That is probably a libc bug, and given that SunOS 4.xhas been end-of-lifed years ago, don't hold your breath for a fix.In addition to that, don't try anything too Unicode-y, especiallywith Encode, and you should be fine in SunOS 4.x.

AUTHOR

The original was written by Andy Dougherty [email protected]drawing heavily on advice from Alan Burlison, Nick Ing-Simmons, Tim Bunce,and many other Solaris users over the years.

Please report any errors, updates, or suggestions to [email protected].

Page index
 
Source : perldoc.perl.org - Official documentation for the Perl programming language
Site maintained by Jon Allen (JJ)     See the project page for more details
Documentation maintained by the Perl 5 Porters
(Sebelumnya) Perl version 5 for RISC OSPerl version 5 on Symbian OS (Berikutnya)