Cari di Perl 
     Perl User Manual
Daftar Isi ☛
(Sebelumnya) Perl version 5.10+ on HaikuPerl version 5 on Hurd (Berikutnya)
Platform Specific

Perl version 5 on Hewlett-Packard Unix (HP-UX) systems

Daftar Isi

NAME

perlhpux - Perl version 5 on Hewlett-Packard Unix (HP-UX) systems

DESCRIPTION

This document describes various features of HP's Unix operating system(HP-UX) that will affect how Perl version 5 (hereafter just Perl) iscompiled and/or runs.

Using perl as shipped with HP-UX

Application release September 2001, HP-UX 11.00 is the first to shipwith Perl. By the time it was perl-5.6.1 in /opt/perl. The firstoccurrence is on CD 5012-7954 and can be installed using

  1.   swinstall -s /cdrom perl
    2.

assuming you have mounted that CD on /cdrom. In this version thefollowing modules were installed:

  1.   ActivePerl::DocTools-0.04   HTML::Parser-3.19   XML::DOM-1.25
    2.  
  2.   Archive::Tar-0.072  HTML::Tagset-3.03   XML::Parser-2.27
    3.  
  3.   Compress::Zlib-1.08 MIME::Base64-2.11   XML::Simple-1.05
    4.  
  4.   Convert::ASN1-0.10  Net-1.07 XML::XPath-1.09
    5.  
  5.   Digest::MD5-2.11 PPM-2.1.5   XML::XSLT-0.32
    6.  
  6.   File::CounterFile-0.12  SOAP::Lite-0.46 libwww-perl-5.51
    7.  
  7.   Font::AFM-1.18  Storable-1.011  libxml-perl-0.07
    8.  
  8.   HTML-Tree-3.11  URI-1.11 perl-ldap-0.23
    9.

That build was a portable hppa-1.1 multithread build that supports largefiles compiled with gcc-2.9-hppa-991112.

If you perform a new installation, then (a newer) Perl will be installedautomatically. Preinstalled HP-UX systems now slao have more recent versionsof Perl and the updated modules.

The official (threaded) builds from HP, as they are shipped on theApplication DVD/CD's are available onhttp://www.software.hp.com/portal/swdepot/displayProductInfo.do?productNumber=PERLfor both PA-RISC and IPF (Itanium Processor Family). They are builtwith the HP ANSI-C compiler. Up till 5.8.8 that was done by ActiveState.

To see what version is included on the DVD (assumed here to be mountedon /cdrom), issue this command:

  1.   # swlist -s /cdrom perl
    2.  
  2.   # perl   D.5.8.8.B  5.8.8 Perl Programming Language
    3.  
  3.  perl.Perl5-32  D.5.8.8.B  32-bit 5.8.8 Perl Programming Language with Extensions
    4.  
  4.  perl.Perl5-64  D.5.8.8.B  64-bit 5.8.8 Perl Programming Language with Extensions
    5.

Using perl from HP's porting centre

HP porting centre tries very hard to keep up with customer demand andrelease updates from the Open Source community. Having precompiledPerl binaries available is obvious.

The HP porting centres are limited in what systems they are allowedto port to and they usually choose the two most recent OS versionsavailable. This means that at the moment of writing, there are onlyHP-UX 11.11 (pa-risc 2.0) and HP-UX 11.23 (Itanium 2) ports availableon the porting centres.

HP has asked the porting centre to move Open Source binariesfrom /opt to /usr/local, so binaries produced since the startof July 2002 are located in /usr/local.

One of HP porting centres URL's is http://hpux.connect.org.uk/The port currently available is built with GNU gcc.

Compiling Perl 5 on HP-UX

When compiling Perl, you must use an ANSI C compiler. The C compilerthat ships with all HP-UX systems is a K&R compiler that should only beused to build new kernels.

Perl can be compiled with either HP's ANSI C compiler or with gcc. Theformer is recommended, as not only can it compile Perl with nodifficulty, but also can take advantage of features listed later thatrequire the use of HP compiler-specific command-line flags.

If you decide to use gcc, make sure your installation is recent andcomplete, and be sure to read the Perl INSTALL file for more gcc-specificdetails.

PA-RISC

HP's HP9000 Unix systems run on HP's own Precision Architecture(PA-RISC) chip. HP-UX used to run on the Motorola MC68000 family ofchips, but any machine with this chip in it is quite obsolete and thisdocument will not attempt to address issues for compiling Perl on theMotorola chipset.

The version of PA-RISC at the time of this document's last update is 2.0,which is also the last there will be. HP PA-RISC systems are usuallyrefered to with model description "HP 9000". The last CPU in this seriesis the PA-8900. Support for PA-RISC architectured machines officiallyends as shown in the following table:

  1.    PA-RISC End-of-Life Roadmap
    2.  
  2.  +--------+----------------+----------------+-----------------+
    3.  
  3.  | HP9000 | Superdome  | PA-8700 | Spring 2011 |
    4.  
  4.  | 4-128  | | PA-8800/sx1000 | Summer 2012 |
    5.  
  5.  | cores  | | PA-8900/sx1000 | 2014 |
    6.  
  6.  | | | PA-8900/sx2000 | 2015 |
    7.  
  7.  +--------+----------------+----------------+-----------------+
    8.  
  8.  | HP9000 | rp7410, rp8400 | PA-8700 | Spring 2011 |
    9.  
  9.  | 2-32   | rp7420, rp8420 | PA-8800/sx1000 | 2012 |
    10.  
  10.  | cores  | rp7440, rp8440 | PA-8900/sx1000 | Autumn 2013 |
    11.  
  11.  | | | PA-8900/sx2000 | 2015 |
    12.  
  12.  +--------+----------------+----------------+-----------------+
    13.  
  13.  | HP9000 | rp44x0 | PA-8700 | Spring 2011 |
    14.  
  14.  | 1-8 | | PA-8800/rp44x0 | 2012 |
    15.  
  15.  | cores  | | PA-8900/rp44x0 | 2014 |
    16.  
  16.  +--------+----------------+----------------+-----------------+
    17.  
  17.  | HP9000 | rp34x0 | PA-8700 | Spring 2011 |
    18.  
  18.  | 1-4 | | PA-8800/rp34x0 | 2012 |
    19.  
  19.  | cores  | | PA-8900/rp34x0 | 2014 |
    20.  
  20.  +--------+----------------+----------------+-----------------+
    21.

From http://www.hp.com/products1/evolution/9000/faqs.html

  1.  The last order date for HP 9000 systems was December 31, 2008.
    2.

A complete list of models at the time the OS was built is in the file/usr/sam/lib/mo/sched.models. The first column corresponds to the lastpart of the output of the "model" command. The second column is thePA-RISC version and the third column is the exact chip type used.(Start browsing at the bottom to prevent confusion ;-)

  1.   # model
    2.  
  2.   9000/800/L1000-44
    3.  
  3.   # grep L1000-44 /usr/sam/lib/mo/sched.models
    4.  
  4.   L1000-44 2.0 PA8500
    5.

Portability Between PA-RISC Versions

An executable compiled on a PA-RISC 2.0 platform will not execute on aPA-RISC 1.1 platform, even if they are running the same version ofHP-UX. If you are building Perl on a PA-RISC 2.0 platform and want thatPerl to also run on a PA-RISC 1.1, the compiler flags +DAportable and+DS32 should be used.

It is no longer possible to compile PA-RISC 1.0 executables on eitherthe PA-RISC 1.1 or 2.0 platforms. The command-line flags are accepted,but the resulting executable will not run when transferred to a PA-RISC1.0 system.

PA-RISC 1.0

The original version of PA-RISC, HP no longer sells any system with this chip.

The following systems contained PA-RISC 1.0 chips:

  1.   600, 635, 645, 808, 815, 822, 825, 832, 834, 835, 840, 842, 845, 850,
    2.  
  2.   852, 855, 860, 865, 870, 890
    3.

PA-RISC 1.1

An upgrade to the PA-RISC design, it shipped for many years in many differentsystem.

The following systems contain with PA-RISC 1.1 chips:

  1.   705, 710, 712, 715, 720, 722, 725, 728, 730, 735, 742, 743, 744, 745,
    2.  
  2.   747, 750, 755, 770, 777, 778, 779, 800, 801, 803, 806, 807, 809, 811,
    3.  
  3.   813, 816, 817, 819, 821, 826, 827, 829, 831, 837, 839, 841, 847, 849,
    4.  
  4.   851, 856, 857, 859, 867, 869, 877, 887, 891, 892, 897, A180, A180C,
    5.  
  5.   B115, B120, B132L, B132L+, B160L, B180L, C100, C110, C115, C120,
    6.  
  6.   C160L, D200, D210, D220, D230, D250, D260, D310, D320, D330, D350,
    7.  
  7.   D360, D410, DX0, DX5, DXO, E25, E35, E45, E55, F10, F20, F30, G30,
    8.  
  8.   G40, G50, G60, G70, H20, H30, H40, H50, H60, H70, I30, I40, I50, I60,
    9.  
  9.   I70, J200, J210, J210XC, K100, K200, K210, K220, K230, K400, K410,
    10.  
  10.   K420, S700i, S715, S744, S760, T500, T520
    11.

PA-RISC 2.0

The most recent upgrade to the PA-RISC design, it added support for64-bit integer data.

As of the date of this document's last update, the following systemscontain PA-RISC 2.0 chips:

  1.   700, 780, 781, 782, 783, 785, 802, 804, 810, 820, 861, 871, 879, 889,
    2.  
  2.   893, 895, 896, 898, 899, A400, A500, B1000, B2000, C130, C140, C160,
    3.  
  3.   C180, C180+, C180-XP, C200+, C400+, C3000, C360, C3600, CB260, D270,
    4.  
  4.   D280, D370, D380, D390, D650, J220, J2240, J280, J282, J400, J410,
    5.  
  5.   J5000, J5500XM, J5600, J7000, J7600, K250, K260, K260-EG, K270, K360,
    6.  
  6.   K370, K380, K450, K460, K460-EG, K460-XP, K470, K570, K580, L1000,
    7.  
  7.   L2000, L3000, N4000, R380, R390, SD16000, SD32000, SD64000, T540,
    8.  
  8.   T600, V2000, V2200, V2250, V2500, V2600
    9.

Just before HP took over Compaq, some systems were renamed. the linkthat contained the explanation is dead, so here's a short summary:

  1.   HP 9000 A-Class servers, now renamed HP Server rp2400 series.
    2.  
  2.   HP 9000 L-Class servers, now renamed HP Server rp5400 series.
    3.  
  3.   HP 9000 N-Class servers, now renamed HP Server rp7400.
    4.  
  4.  
  5.   rp2400, rp2405, rp2430, rp2450, rp2470, rp3410, rp3440, rp4410,
    6.  
  6.   rp4440, rp5400, rp5405, rp5430, rp5450, rp5470, rp7400, rp7405,
    7.  
  7.   rp7410, rp7420, rp7440, rp8400, rp8420, rp8440, Superdome
    8.

The current naming convention is:

  1.   aadddd
    2.  
  2.   ||||`+- 00 - 99 relative capacity & newness (upgrades, etc.)
    3.  
  3.   |||`--- unique number for each architecture to ensure different
    4.  
  4.   ||| systems do not have the same numbering across
    5.  
  5.   ||| architectures
    6.  
  6.   ||`---- 1 - 9 identifies family and/or relative positioning
    7.  
  7.   ||
    8.  
  8.   |`----- c = ia32 (cisc)
    9.  
  9.   |   p = pa-risc
    10.  
  10.   |   x = ia-64 (Itanium & Itanium 2)
    11.  
  11.   |   h = housing
    12.  
  12.   `------ t = tower
    13.  
  13.   r = rack optimized
    14.  
  14.   s = super scalable
    15.  
  15.   b = blade
    16.  
  16.   sa = appliance
    17.

Itanium Processor Family (IPF) and HP-UX

HP-UX also runs on the new Itanium processor. This requires the useof a different version of HP-UX (currently 11.23 or 11i v2), and withthe exception of a few differences detailed below and in later sections,Perl should compile with no problems.

Although PA-RISC binaries can run on Itanium systems, you should notattempt to use a PA-RISC version of Perl on an Itanium system. This isbecause shared libraries created on an Itanium system cannot be loadedwhile running a PA-RISC executable.

HP Itanium 2 systems are usually refered to with model description"HP Integrity".

Itanium, Itanium 2 & Madison 6

HP also ships servers with the 128-bit Itanium processor(s). The cx26x0is told to have Madison 6. As of the date of this document's last update,the following systems contain Itanium or Itanium 2 chips (this is likelyto be out of date):

  1.   BL60p, BL860c, BL870c, cx2600, cx2620, rx1600, rx1620, rx2600,
    2.  
  2.   rx2600hptc, rx2620, rx2660, rx3600, rx4610, rx4640, rx5670,
    3.  
  3.   rx6600, rx7420, rx7620, rx7640, rx8420, rx8620, rx8640, rx9610,
    4.  
  4.   sx1000, sx2000
    5.

To see all about your machine, type

  1.   # model
    2.  
  2.   ia64 hp server rx2600
    3.  
  3.   # /usr/contrib/bin/machinfo
    4.

HP-UX versions

Not all architectures (PA = PA-RISC, IPF = Itanium Processor Family)support all versions of HP-UX, here is a short list

  1.   HP-UX version  Kernel  Architecture
    2.  
  2.   -------------  ------  ------------
    3.  
  3.   10.20  32 bit  PA
    4.  
  4.   11.00  32/64   PA
    5.  
  5.   11.11  11i v1  32/64   PA
    6.  
  6.   11.22  11i v2 64 IPF
    7.  
  7.   11.23  11i v2 64   PA & IPF
    8.  
  8.   11.31  11i v3 64   PA & IPF
    9.

See for the full list of hardware/OS support and expected end-of-lifehttp://www.hp.com/go/hpuxservermatrix

Building Dynamic Extensions on HP-UX

HP-UX supports dynamically loadable libraries (shared libraries).Shared libraries end with the suffix .sl. On Itanium systems,they end with the suffix .so.

Shared libraries created on a platform using a particular PA-RISCversion are not usable on platforms using an earlier PA-RISC version bydefault. However, this backwards compatibility may be enabled using thesame +DAportable compiler flag (with the same PA-RISC 1.0 caveatmentioned above).

Shared libraries created on an Itanium platform cannot be loaded ona PA-RISC platform. Shared libraries created on a PA-RISC platformcan only be loaded on an Itanium platform if it is a PA-RISC executablethat is attempting to load the PA-RISC library. A PA-RISC sharedlibrary cannot be loaded into an Itanium executable nor vice-versa.

To create a shared library, the following steps must be performed:

  1.   1. Compile source modules with +z or +Z flag to create a .o module
    2.  
  2.  which contains Position-Independent Code (PIC).  The linker will
    3.  
  3.  tell you in the next step if +Z was needed.
    4.  
  4.  (For gcc, the appropriate flag is -fpic or -fPIC.)
    5.  
  5.  
  6.   2. Link the shared library using the -b flag.  If the code calls
    7.  
  7.  any functions in other system libraries (e.g., libm), it must
    8.  
  8.  be included on this line.
    9.

(Note that these steps are usually handled automatically by the extension'sMakefile).

If these dependent libraries are not listed at shared library creationtime, you will get fatal "Unresolved symbol" errors at run time when thelibrary is loaded.

You may create a shared library that refers to another library, whichmay be either an archive library or a shared library. If this secondlibrary is a shared library, this is called a "dependent library". Thedependent library's name is recorded in the main shared library, but itis not linked into the shared library. Instead, it is loaded when themain shared library is loaded. This can cause problems if you build anextension on one system and move it to another system where thelibraries may not be located in the same place as on the first system.

If the referred library is an archive library, then it is treated as asimple collection of .o modules (all of which must contain PIC). Thesemodules are then linked into the shared library.

Note that it is okay to create a library which contains a dependentlibrary that is already linked into perl.

Some extensions, like DB_File and Compress::Zlib use/require prebuiltlibraries for the perl extensions/modules to work. If these librariesare built using the default configuration, it might happen that yourun into an error like "invalid loader fixup" during load phase.HP is aware of this problem. Search the HP-UX cxx-dev forums fordiscussions about the subject. The short answer is that everything(all libraries, everything) must be compiled with +z or +Z to bePIC (position independent code). (For gcc, that would be-fpic or -fPIC). In HP-UX 11.00 or newer the linkererror message should tell the name of the offending object file.

A more general approach is to intervene manually, as with an example forthe DB_File module, which requires SleepyCat's libdb.sl:

  1.   # cd .../db-3.2.9/build_unix
    2.  
  2.   # vi Makefile
    3.  
  3.   ... add +Z to all cflags to create shared objects
    4.  
  4.   CFLAGS= -c $(CPPFLAGS) +Z -Ae +O2 +Onolimit \
    5.  
  5.   -I/usr/local/include -I/usr/include/X11R6
    6.  
  6.   CXXFLAGS=   -c $(CPPFLAGS) +Z -Ae +O2 +Onolimit \
    7.  
  7.   -I/usr/local/include -I/usr/include/X11R6
    8.  
  8.  
  9.   # make clean
    10.  
  10.   # make
    11.  
  11.   # mkdir tmp
    12.  
  12.   # cd tmp
    13.  
  13.   # ar x ../libdb.a
    14.  
  14.   # ld -b -o libdb-3.2.sl *.o
    15.  
  15.   # mv libdb-3.2.sl /usr/local/lib
    16.  
  16.   # rm *.o
    17.  
  17.   # cd /usr/local/lib
    18.  
  18.   # rm -f libdb.sl
    19.  
  19.   # ln -s libdb-3.2.sl libdb.sl
    20.  
  20.  
  21.   # cd .../DB_File-1.76
    22.  
  22.   # make distclean
    23.  
  23.   # perl Makefile.PL
    24.  
  24.   # make
    25.  
  25.   # make test
    26.  
  26.   # make install
    27.

As of db-4.2.x it is no longer needed to do this by hand. Sleepycathas changed the configuration process to add +z on HP-UX automatically.

  1.   # cd .../db-4.2.25/build_unix
    2.  
  2.   # env CFLAGS=+DD64 LDFLAGS=+DD64 ../dist/configure
    3.

should work to generate 64bit shared libraries for HP-UX 11.00 and 11i.

It is no longer possible to link PA-RISC 1.0 shared libraries (eventhough the command-line flags are still present).

PA-RISC and Itanium object files are not interchangeable. Althoughyou may be able to use ar to create an archive library of PA-RISCobject files on an Itanium system, you cannot link against it usingan Itanium link editor.

The HP ANSI C Compiler

When using this compiler to build Perl, you should make sure that theflag -Aa is added to the cpprun and cppstdin variables in the config.shfile (though see the section on 64-bit perl below). If you are using arecent version of the Perl distribution, these flags are set automatically.

Even though HP-UX 10.20 and 11.00 are not actively maintained by HPanymore, updates for the HP ANSI C compiler are still available fromtime to time, and it might be advisable to see if updates are applicable.At the moment of writing, the latests available patches for 11.00 thatshould be applied are PHSS_35098, PHSS_35175, PHSS_35100, PHSS_33036,and PHSS_33902). If you have a SUM account, you can use it to searchfor updates/patches. Enter "ANSI" as keyword.

The GNU C Compiler

When you are going to use the GNU C compiler (gcc), and you don't havegcc yet, you can either build it yourself from the sources (availablefrom e.g. http://gcc.gnu.org/mirrors.html) or fetcha prebuilt binary from the HP porting center. gcc prebuilds can befetched fromhttp://h21007.www2.hp.com/dspp/tech/tech_TechSoftwareDetailPage_IDX/1,1703,547,00.html(Browse through the list, because there are often multiple versions ofthe same package available).

Above mentioned distributions are depots. H.Merijn Brand has made prebuiltgcc binaries available on http://mirrors.develooper.com/hpux/ and/orhttp://www.cmve.net/~merijn/ for HP-UX 10.20, HP-UX 11.00, HP-UX 11.11(HP-UX 11i v1), and HP-UX 11.23 (HP-UX 11i v2) in both 32- and 64-bitversions. These are bzipped tar archives that also include recent GNUbinutils and GNU gdb. Read the instructions on that page to rebuild gccusing itself.

On PA-RISC you need a different compiler for 32-bit applications and for64-bit applications. On PA-RISC, 32-bit objects and 64-bit objects donot mix. Period. There is no different behaviour for HP C-ANSI-C or GNUgcc. So if you require your perl binary to use 64-bit libraries, likeOracle-64bit, you MUST build a 64-bit perl.

Building a 64-bit capable gcc on PA-RISC from source is possible only whenyou have the HP C-ANSI C compiler or an already working 64-bit binary ofgcc available. Best performance for perl is achieved with HP's nativecompiler.

Using Large Files with Perl on HP-UX

Beginning with HP-UX version 10.20, files larger than 2GB (2^31 bytes)may be created and manipulated. Three separate methods of doing thisare available. Of these methods, the best method for Perl is to compileusing the -Duselargefiles flag to Configure. This causes Perl to becompiled using structures and functions in which these are 64 bits wide,rather than 32 bits wide. (Note that this will only work with HP's ANSIC compiler. If you want to compile Perl using gcc, you will have to geta version of the compiler that supports 64-bit operations. See above forwhere to find it.)

There are some drawbacks to this approach. One is that any extensionwhich calls any file-manipulating C function will need to be recompiled(just follow the usual "perl Makefile.PL; make; make test; make install"procedure).

The list of functions that will need to recompiled is: creat, fgetpos, fopen, freopen, fsetpos, fstat, fstatvfs, fstatvfsdev, ftruncate, ftw, lockf, lseek, lstat, mmap, nftw, open, prealloc, stat, statvfs, statvfsdev, tmpfile, truncate, getrlimit, setrlimit

Another drawback is only valid for Perl versions before 5.6.0. Thisdrawback is that the seek and tell functions (both the builtin versionand POSIX module version) will not perform correctly.

It is strongly recommended that you use this flag when you runConfigure. If you do not do this, but later answer the question aboutlarge files when Configure asks you, you may get a configuration thatcannot be compiled, or that does not function as expected.

Threaded Perl on HP-UX

It is possible to compile a version of threaded Perl on any version ofHP-UX before 10.30, but it is strongly suggested that you be running onHP-UX 11.00 at least.

To compile Perl with threads, add -Dusethreads to the arguments ofConfigure. Verify that the -D_POSIX_C_SOURCE=199506L compiler flag isautomatically added to the list of flags. Also make sure that -lpthreadis listed before -lc in the list of libraries to link Perl with. Thehints provided for HP-UX during Configure will try very hard to getthis right for you.

HP-UX versions before 10.30 require a separate installation of a POSIXthreads library package. Two examples are the HP DCE package, availableon "HP-UX Hardware Extensions 3.0, Install and Core OS, Release 10.20,April 1999 (B3920-13941)" or the Freely available PTH package, availableon H.Merijn's site (http://mirrors.develooper.com/hpux/). The use of PTHwill be unsupported in perl-5.12 and up and is rather buggy in 5.11.x.

If you are going to use the HP DCE package, the library used for threadingis /usr/lib/libcma.sl, but there have been multiple updates of thatlibrary over time. Perl will build with the first version, but itwill not pass the test suite. Older Oracle versions might be a compellingreason not to update that library, otherwise please find a newer versionin one of the following patches: PHSS_19739, PHSS_20608, or PHSS_23672

reformatted output:

  1.   d3:/usr/lib 106 > what libcma-*.1
    2.  
  2.   libcma-00000.1:
    3.  
  3.  HP DCE/9000 1.5   Module: libcma.sl (Export)
    4.  
  4.    Date: Apr 29 1996 22:11:24
    5.  
  5.   libcma-19739.1:
    6.  
  6.  HP DCE/9000 1.5 PHSS_19739-40 Module: libcma.sl (Export)
    7.  
  7.    Date: Sep  4 1999 01:59:07
    8.  
  8.   libcma-20608.1:
    9.  
  9.  HP DCE/9000 1.5 PHSS_20608 Module: libcma.1 (Export)
    10.  
  10.    Date: Dec  8 1999 18:41:23
    11.  
  11.   libcma-23672.1:
    12.  
  12.  HP DCE/9000 1.5 PHSS_23672 Module: libcma.1 (Export)
    13.  
  13.    Date: Apr  9 2001 10:01:06
    14.  
  14.   d3:/usr/lib 107 >
    15.

If you choose for the PTH package, use swinstall to install pth inthe default location (/opt/pth), and then make symbolic links to thelibraries from /usr/lib

  1.   # cd /usr/lib
    2.  
  2.   # ln -s /opt/pth/lib/libpth* .
    3.

For building perl to support Oracle, it needs to be linked with libcland libpthread. So even if your perl is an unthreaded build, theselibraries might be required. See "Oracle on HP-UX" below.

64-bit Perl on HP-UX

Beginning with HP-UX 11.00, programs compiled under HP-UX can takeadvantage of the LP64 programming environment (LP64 means Longs andPointers are 64 bits wide), in which scalar variables will be ableto hold numbers larger than 2^32 with complete precision. Perl hasproven to be consistent and reliable in 64bit mode since 5.8.1 onall HP-UX 11.xx.

As of the date of this document, Perl is fully 64-bit compliant onHP-UX 11.00 and up for both cc- and gcc builds. If you are about tobuild a 64-bit perl with GNU gcc, please read the gcc section carefully.

Should a user have the need for compiling Perl in the LP64 environment,use the -Duse64bitall flag to Configure. This will force Perl to becompiled in a pure LP64 environment (with the +DD64 flag for HP C-ANSI-C,with no additional options for GNU gcc 64-bit on PA-RISC, and with-mlp64 for GNU gcc on Itanium).If you want to compile Perl using gcc, you will have to get a version ofthe compiler that supports 64-bit operations.)

You can also use the -Duse64bitint flag to Configure. Although thereare some minor differences between compiling Perl with this flag versusthe -Duse64bitall flag, they should not be noticeable from a Perl user'sperspective. When configuring -Duse64bitint using a 64bit gcc on apa-risc architecture, -Duse64bitint is silently promoted to -Duse64bitall.

In both cases, it is strongly recommended that you use these flags whenyou run Configure. If you do not use do this, but later answer thequestions about 64-bit numbers when Configure asks you, you may get aconfiguration that cannot be compiled, or that does not function asexpected.

Oracle on HP-UX

Using perl to connect to Oracle databases through DBI and DBD::Oraclehas caused a lot of people many headaches. Read README.hpux in theDBD::Oracle for much more information. The reason to mention it hereis that Oracle requires a perl built with libcl and libpthread, thelatter even when perl is build without threads. Building perl usingall defaults, but still enabling to build DBD::Oracle later on can beachieved using

  1.   Configure -A prepend:libswanted='cl pthread ' ...
    2.

Do not forget the space before the trailing quote.

Also note that this does not (yet) work with all configurations,it is known to fail with 64-bit versions of GCC.

GDBM and Threads on HP-UX

If you attempt to compile Perl with (POSIX) threads on an 11.X systemand also link in the GDBM library, then Perl will immediately core dumpwhen it starts up. The only workaround at this point is to relink theGDBM library under 11.X, then relink it into Perl.

the error might show something like:

Pthread internal error: message: __libc_reinit() failed, file: ../pthreads/pthread.c, line: 1096Return Pointer is 0xc082bf33sh: 5345 Quit(coredump)

and Configure will give up.

NFS filesystems and utime(2) on HP-UX

If you are compiling Perl on a remotely-mounted NFS filesystem, the testio/fs.t may fail on test #18. This appears to be a bug in HP-UX and nofix is currently available.

HP-UX Kernel Parameters (maxdsiz) for Compiling Perl

By default, HP-UX comes configured with a maximum data segment size of64MB. This is too small to correctly compile Perl with the maximumoptimization levels. You can increase the size of the maxdsiz kernelparameter through the use of SAM.

When using the GUI version of SAM, click on the Kernel Configurationicon, then the Configurable Parameters icon. Scroll down and selectthe maxdsiz line. From the Actions menu, select the Modify ConfigurableParameter item. Insert the new formula into the Formula/Value box.Then follow the instructions to rebuild your kernel and reboot yoursystem.

In general, a value of 256MB (or "256*1024*1024") is sufficient forPerl to compile at maximum optimization.

nss_delete core dump from op/pwent or op/grent

You may get a bus error core dump from the op/pwent or op/grenttests. If compiled with -g you will see a stack trace much likethe following:

  1.   #0  0xc004216c in  () from /usr/lib/libc.2
    2.  
  2.   #1  0xc00d7550 in __nss_src_state_destr () from /usr/lib/libc.2
    3.  
  3.   #2  0xc00d7768 in __nss_src_state_destr () from /usr/lib/libc.2
    4.  
  4.   #3  0xc00d78a8 in nss_delete () from /usr/lib/libc.2
    5.  
  5.   #4  0xc01126d8 in endpwent () from /usr/lib/libc.2
    6.  
  6.   #5  0xd1950 in Perl_pp_epwent () from ./perl
    7.  
  7.   #6  0x94d3c in Perl_runops_standard () from ./perl
    8.  
  8.   #7  0x23728 in S_run_body () from ./perl
    9.  
  9.   #8  0x23428 in perl_run () from ./perl
    10.  
  10.   #9  0x2005c in main () from ./perl
    11.

The key here is the nss_delete call. One workaround for thisbug seems to be to create add to the file /etc/nsswitch.conf(at least) the following lines

  1.   group: files
    2.  
  2.   passwd: files
    3.

Whether you are using NIS does not matter. Amazingly enough,the same bug also affects Solaris.

error: pasting ")" and "l" does not give a valid preprocessing token

There seems to be a broken system header file in HP-UX 11.00 thatbreaks perl building in 32bit mode with GNU gcc-4.x causing thiserror. The same file for HP-UX 11.11 (even though the file is older)does not show this failure, and has the correct definition, so thebest fix is to patch the header to match:

  1.  --- /usr/include/inttypes.h  2001-04-20 18:42:14 +0200
    2.  
  2.  +++ /usr/include/inttypes.h  2000-11-14 09:00:00 +0200
    3.  
  3.  @@ -72,7 +72,7 @@
    4.  
  4.   #define UINT32_C(__c)   __CONCAT_U__(__c)
    5.  
  5.   #else /* __LP64 */
    6.  
  6.   #define INT32_C(__c) __CONCAT__(__c,l)
    7.  
  7.  -#define UINT32_C(__c)   __CONCAT__(__CONCAT_U__(__c),l)
    8.  
  8.  +#define UINT32_C(__c)   __CONCAT__(__c,ul)
    9.  
  9.   #endif /* __LP64 */
    10.  
  10.  
  11.   #define INT64_C(__c) __CONCAT_L__(__c,l)
    12.

Miscellaneous

HP-UX 11 Y2K patch "Y2K-1100 B.11.00.B0125 HP-UX Core OS Year 2000Patch Bundle" has been reported to break the io/fs test #18 whichtests whether utime() can change timestamps. The Y2K patch seems tobreak utime() so that over NFS the timestamps do not get changed(on local filesystems utime() still works). This has probably beenfixed on your system by now.

AUTHOR

H.Merijn Brand <[email protected]>Jeff Okamoto <[email protected]>

With much assistance regarding shared libraries from Marc Sabatella.

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.10+ on HaikuPerl version 5 on Hurd (Berikutnya)