{ "content": [ { "type": "text", "text": "# PERLHPUX (man)\n\n## NAME\n\nperlhpux - Perl version 5 on Hewlett-Packard Unix (HP-UX) systems\n\n## DESCRIPTION\n\nThis document describes various features of HP's Unix operating system (HP-UX) that will\naffect how Perl version 5 (hereafter just Perl) is compiled and/or runs.\n\n## Sections\n\n- **NAME**\n- **DESCRIPTION** (23 subsections)\n- **Miscellaneous**\n- **AUTHOR**\n\nUse structuredContent.sections for detailed options, examples, and full documentation.\n" } ], "structuredContent": { "command": "PERLHPUX", "section": "", "mode": "man", "summary": "perlhpux - Perl version 5 on Hewlett-Packard Unix (HP-UX) systems", "synopsis": null, "tldr_summary": null, "tldr_examples": [], "tldr_source": null, "flags": [], "examples": [], "see_also": [], "section_outline": [ { "name": "NAME", "lines": 2, "subsections": [] }, { "name": "DESCRIPTION", "lines": 3, "subsections": [ { "name": "Using perl as shipped with HP-UX", "lines": 43 }, { "name": "Using perl from HP's porting centre", "lines": 14 }, { "name": "Other prebuilt perl binaries", "lines": 4 }, { "name": "Compiling Perl 5 on HP-UX", "lines": 56 }, { "name": "PA-RISC 1.0", "lines": 7 }, { "name": "PA-RISC 1.1", "lines": 15 }, { "name": "PA-RISC 2.0", "lines": 44 }, { "name": "Portability Between PA-RISC Versions", "lines": 9 }, { "name": "Itanium Processor Family (IPF) and HP-UX", "lines": 10 }, { "name": "Itanium, Itanium 2 & Madison 6", "lines": 15 }, { "name": "HP-UX versions", "lines": 15 }, { "name": "Building Dynamic Extensions on HP-UX", "lines": 98 }, { "name": "The HP ANSI C Compiler", "lines": 12 }, { "name": "The GNU C Compiler", "lines": 24 }, { "name": "Using Large Files with Perl on HP-UX", "lines": 30 }, { "name": "Threaded Perl on HP-UX", "lines": 48 }, { "name": "64-bit Perl on HP-UX", "lines": 25 }, { "name": "Oracle on HP-UX", "lines": 13 }, { "name": "GDBM and Threads on HP-UX", "lines": 11 }, { "name": "NFS filesystems and utime(2) on HP-UX", "lines": 3 }, { "name": "HP-UX Kernel Parameters (maxdsiz) for Compiling Perl", "lines": 37 }, { "name": "error: pasting \")\" and \"l\" does not give a valid preprocessing token", "lines": 17 }, { "name": "Redeclaration of \"sendpath\" with a different storage class specifier", "lines": 22 } ] }, { "name": "Miscellaneous", "lines": 5, "subsections": [] }, { "name": "AUTHOR", "lines": 7, "subsections": [] } ], "sections": { "NAME": { "content": "perlhpux - Perl version 5 on Hewlett-Packard Unix (HP-UX) systems\n", "subsections": [] }, "DESCRIPTION": { "content": "This document describes various features of HP's Unix operating system (HP-UX) that will\naffect how Perl version 5 (hereafter just Perl) is compiled and/or runs.\n", "subsections": [ { "name": "Using perl as shipped with HP-UX", "content": "Application release September 2001, HP-UX 11.00 is the first to ship with Perl. By the time\nit was perl-5.6.1 in /opt/perl. The first occurrence is on CD 5012-7954 and can be installed\nusing\n\nswinstall -s /cdrom perl\n\nassuming you have mounted that CD on /cdrom.\n\nThat build was a portable hppa-1.1 multithread build that supports large files compiled with\ngcc-2.9-hppa-991112.\n\nIf you perform a new installation, then (a newer) Perl will be installed automatically. Pre-\ninstalled HP-UX systems now have more recent versions of Perl and the updated modules.\n\nThe official (threaded) builds from HP, as they are shipped on the Application DVD/CD's are\navailable on\n for both\nPA-RISC and IPF (Itanium Processor Family). They are built with the HP ANSI-C compiler. Up\ntill 5.8.8 that was done by ActiveState.\n\nTo see what version is included on the DVD (assumed here to be mounted on /cdrom), issue this\ncommand:\n\n# swlist -s /cdrom perl\n# perl D.5.8.8.B 5.8.8 Perl Programming Language\nperl.Perl5-32 D.5.8.8.B 32-bit 5.8.8 Perl Programming Language\nwith Extensions\nperl.Perl5-64 D.5.8.8.B 64-bit 5.8.8 Perl Programming Language\nwith Extensions\n\nTo see what is installed on your system:\n\n# swlist -R perl\n# perl E.5.8.8.J Perl Programming Language\n# perl.Perl5-32 E.5.8.8.J 32-bit Perl Programming Language\nwith Extensions\nperl.Perl5-32.PERL-MAN E.5.8.8.J 32-bit Perl Man Pages for IA\nperl.Perl5-32.PERL-RUN E.5.8.8.J 32-bit Perl Binaries for IA\n# perl.Perl5-64 E.5.8.8.J 64-bit Perl Programming Language\nwith Extensions\nperl.Perl5-64.PERL-MAN E.5.8.8.J 64-bit Perl Man Pages for IA\nperl.Perl5-64.PERL-RUN E.5.8.8.J 64-bit Perl Binaries for IA\n" }, { "name": "Using perl from HP's porting centre", "content": "HP porting centre tries to keep up with customer demand and release updates from the Open\nSource community. Having precompiled Perl binaries available is obvious, though \"up-to-date\"\nis something relative. At the moment of writing perl-5.10.1 and 5.28.0 were available.\n\nThe HP porting centres are limited in what systems they are allowed to port to and they\nusually choose the two most recent OS versions available.\n\nHP has asked the porting centre to move Open Source binaries from /opt to /usr/local, so\nbinaries produced since the start of July 2002 are located in /usr/local.\n\nOne of HP porting centres URL's is The port currently available\nis built with GNU gcc. As porting modern GNU gcc is extremely hard on HP-UX, they are stuck\nat version gcc-4.2.3.\n" }, { "name": "Other prebuilt perl binaries", "content": "To get more perl depots for the whole range of HP-UX, visit H.Merijn Brand's site at\n. Carefully read the notes to see if the available\nversions suit your needs.\n" }, { "name": "Compiling Perl 5 on HP-UX", "content": "When compiling Perl, you must use an ANSI C compiler. The C compiler that ships with all HP-\nUX systems is a K&R compiler that should only be used to build new kernels.\n\nPerl can be compiled with either HP's ANSI C compiler or with gcc. The former is\nrecommended, as not only can it compile Perl with no difficulty, but also can take advantage\nof features listed later that require the use of HP compiler-specific command-line flags.\n\nIf you decide to use gcc, make sure your installation is recent and complete, and be sure to\nread the Perl INSTALL file for more gcc-specific details.\n\nPA-RISC\nThe last and final version of PA-RISC is 2.0, HP no longer sells any system with these CPU's.\n\nHP's HP9000 Unix systems run on HP's own Precision Architecture (PA-RISC) chip. HP-UX used\nto run on the Motorola MC68000 family of chips, but any machine with this chip in it is quite\nobsolete and this document will not attempt to address issues for compiling Perl on the\nMotorola chipset. Even though PA-RISC hardware is not sold anymore, a lot of machines still\nrunning on these CPU's can be found in the wild.\n\nThe last order date for HP 9000 systems was December 31, 2008.\n\nHP PA-RISC systems are usually referred to with model description \"HP 9000\". The last CPU in\nthis series is the PA-8900. Support for PA-RISC architectured machines officially ended as\nshown in the following table:\n\nPA-RISC End-of-Life Roadmap\n+--------+----------------+----------------+-----------------+\n| HP9000 | Superdome | PA-8700 | Spring 2011 |\n| 4-128 | | PA-8800/sx1000 | Summer 2012 |\n| cores | | PA-8900/sx1000 | 2014 |\n| | | PA-8900/sx2000 | 2015 |\n+--------+----------------+----------------+-----------------+\n| HP9000 | rp7410, rp8400 | PA-8700 | Spring 2011 |\n| 2-32 | rp7420, rp8420 | PA-8800/sx1000 | 2012 |\n| cores | rp7440, rp8440 | PA-8900/sx1000 | Autumn 2013 |\n| | | PA-8900/sx2000 | 2015 |\n+--------+----------------+----------------+-----------------+\n| HP9000 | rp44x0 | PA-8700 | Spring 2011 |\n| 1-8 | | PA-8800/rp44x0 | 2012 |\n| cores | | PA-8900/rp44x0 | 2014 |\n+--------+----------------+----------------+-----------------+\n| HP9000 | rp34x0 | PA-8700 | Spring 2011 |\n| 1-4 | | PA-8800/rp34x0 | 2012 |\n| cores | | PA-8900/rp34x0 | 2014 |\n+--------+----------------+----------------+-----------------+\n\nA complete list of models at the time the OS was built is in the file\n/usr/sam/lib/mo/sched.models. The first column corresponds to the last part of the output of\nthe \"model\" command. The second column is the PA-RISC version and the third column is the\nexact chip type used. (Start browsing at the bottom to prevent confusion ;-)\n\n# model\n9000/800/L1000-44\n# grep L1000-44 /usr/sam/lib/mo/sched.models\nL1000-44 2.0 PA8500\n" }, { "name": "PA-RISC 1.0", "content": "The original version of PA-RISC, HP no longer sells any system with this chip.\n\nThe following systems contained PA-RISC 1.0 chips:\n\n600, 635, 645, 808, 815, 822, 825, 832, 834, 835, 840, 842, 845, 850,\n852, 855, 860, 865, 870, 890\n" }, { "name": "PA-RISC 1.1", "content": "An upgrade to the PA-RISC design, it shipped for many years in many different system.\n\nThe following systems contain with PA-RISC 1.1 chips:\n\n705, 710, 712, 715, 720, 722, 725, 728, 730, 735, 742, 743, 744, 745,\n747, 750, 755, 770, 777, 778, 779, 800, 801, 803, 806, 807, 809, 811,\n813, 816, 817, 819, 821, 826, 827, 829, 831, 837, 839, 841, 847, 849,\n851, 856, 857, 859, 867, 869, 877, 887, 891, 892, 897, A180, A180C,\nB115, B120, B132L, B132L+, B160L, B180L, C100, C110, C115, C120,\nC160L, D200, D210, D220, D230, D250, D260, D310, D320, D330, D350,\nD360, D410, DX0, DX5, DXO, E25, E35, E45, E55, F10, F20, F30, G30,\nG40, G50, G60, G70, H20, H30, H40, H50, H60, H70, I30, I40, I50, I60,\nI70, J200, J210, J210XC, K100, K200, K210, K220, K230, K400, K410,\nK420, S700i, S715, S744, S760, T500, T520\n" }, { "name": "PA-RISC 2.0", "content": "The most recent upgrade to the PA-RISC design, it added support for 64-bit integer data.\n\nAs of the date of this document's last update, the following systems contain PA-RISC 2.0\nchips:\n\n700, 780, 781, 782, 783, 785, 802, 804, 810, 820, 861, 871, 879, 889,\n893, 895, 896, 898, 899, A400, A500, B1000, B2000, C130, C140, C160,\nC180, C180+, C180-XP, C200+, C400+, C3000, C360, C3600, CB260, D270,\nD280, D370, D380, D390, D650, J220, J2240, J280, J282, J400, J410,\nJ5000, J5500XM, J5600, J7000, J7600, K250, K260, K260-EG, K270, K360,\nK370, K380, K450, K460, K460-EG, K460-XP, K470, K570, K580, L1000,\nL2000, L3000, N4000, R380, R390, SD16000, SD32000, SD64000, T540,\nT600, V2000, V2200, V2250, V2500, V2600\n\nJust before HP took over Compaq, some systems were renamed. the link that contained the\nexplanation is dead, so here's a short summary:\n\nHP 9000 A-Class servers, now renamed HP Server rp2400 series.\nHP 9000 L-Class servers, now renamed HP Server rp5400 series.\nHP 9000 N-Class servers, now renamed HP Server rp7400.\n\nrp2400, rp2405, rp2430, rp2450, rp2470, rp3410, rp3440, rp4410,\nrp4440, rp5400, rp5405, rp5430, rp5450, rp5470, rp7400, rp7405,\nrp7410, rp7420, rp7440, rp8400, rp8420, rp8440, Superdome\n\nThe current naming convention is:\n\naadddd\n||||`+- 00 - 99 relative capacity & newness (upgrades, etc.)\n|||`--- unique number for each architecture to ensure different\n||| systems do not have the same numbering across\n||| architectures\n||`---- 1 - 9 identifies family and/or relative positioning\n||\n|`----- c = ia32 (cisc)\n| p = pa-risc\n| x = ia-64 (Itanium & Itanium 2)\n| h = housing\n`------ t = tower\nr = rack optimized\ns = super scalable\nb = blade\nsa = appliance\n" }, { "name": "Portability Between PA-RISC Versions", "content": "An executable compiled on a PA-RISC 2.0 platform will not execute on a PA-RISC 1.1 platform,\neven if they are running the same version of HP-UX. If you are building Perl on a PA-RISC\n2.0 platform and want that Perl to also run on a PA-RISC 1.1, the compiler flags +DAportable\nand +DS32 should be used.\n\nIt is no longer possible to compile PA-RISC 1.0 executables on either the PA-RISC 1.1 or 2.0\nplatforms. The command-line flags are accepted, but the resulting executable will not run\nwhen transferred to a PA-RISC 1.0 system.\n" }, { "name": "Itanium Processor Family (IPF) and HP-UX", "content": "HP-UX also runs on the newer Itanium processor. This requires the use of HP-UX version 11.23\n(11i v2) or 11.31 (11i v3), and with the exception of a few differences detailed below and in\nlater sections, Perl should compile with no problems.\n\nAlthough PA-RISC binaries can run on Itanium systems, you should not attempt to use a PA-RISC\nversion of Perl on an Itanium system. This is because shared libraries created on an Itanium\nsystem cannot be loaded while running a PA-RISC executable.\n\nHP Itanium 2 systems are usually referred to with model description \"HP Integrity\".\n" }, { "name": "Itanium, Itanium 2 & Madison 6", "content": "HP also ships servers with the 128-bit Itanium processor(s). The cx26x0 is told to have\nMadison 6. As of the date of this document's last update, the following systems contain\nItanium or Itanium 2 chips (this is likely to be out of date):\n\nBL60p, BL860c, BL870c, BL890c, cx2600, cx2620, rx1600, rx1620, rx2600,\nrx2600hptc, rx2620, rx2660, rx2800, rx3600, rx4610, rx4640, rx5670,\nrx6600, rx7420, rx7620, rx7640, rx8420, rx8620, rx8640, rx9610,\nsx1000, sx2000\n\nTo see all about your machine, type\n\n# model\nia64 hp server rx2600\n# /usr/contrib/bin/machinfo\n" }, { "name": "HP-UX versions", "content": "Not all architectures (PA = PA-RISC, IPF = Itanium Processor Family) support all versions of\nHP-UX, here is a short list\n\nHP-UX version Kernel Architecture End-of-factory support\n------------- ------ ------------ ----------------------------------\n10.20 32 bit PA 30-Jun-2003\n11.00 32/64 PA 31-Dec-2006\n11.11 11i v1 32/64 PA 31-Dec-2015\n11.22 11i v2 64 IPF 30-Apr-2004\n11.23 11i v2 64 PA & IPF 31-Dec-2015\n11.31 11i v3 64 PA & IPF 31-Dec-2020 (PA) 31-Dec-2025 (IPF)\n\nSee for the full list of hardware/OS support and expected end-of-life\n\n" }, { "name": "Building Dynamic Extensions on HP-UX", "content": "HP-UX supports dynamically loadable libraries (shared libraries). Shared libraries end with\nthe suffix .sl. On Itanium systems, they end with the suffix .so.\n\nShared libraries created on a platform using a particular PA-RISC version are not usable on\nplatforms using an earlier PA-RISC version by default. However, this backwards compatibility\nmay be enabled using the same +DAportable compiler flag (with the same PA-RISC 1.0 caveat\nmentioned above).\n\nShared libraries created on an Itanium platform cannot be loaded on a PA-RISC platform.\nShared libraries created on a PA-RISC platform can only be loaded on an Itanium platform if\nit is a PA-RISC executable that is attempting to load the PA-RISC library. A PA-RISC shared\nlibrary cannot be loaded into an Itanium executable nor vice-versa.\n\nTo create a shared library, the following steps must be performed:\n\n1. Compile source modules with +z or +Z flag to create a .o module\nwhich contains Position-Independent Code (PIC). The linker will\ntell you in the next step if +Z was needed.\n(For gcc, the appropriate flag is -fpic or -fPIC.)\n\n2. Link the shared library using the -b flag. If the code calls\nany functions in other system libraries (e.g., libm), it must\nbe included on this line.\n\n(Note that these steps are usually handled automatically by the extension's Makefile).\n\nIf these dependent libraries are not listed at shared library creation time, you will get\nfatal \"Unresolved symbol\" errors at run time when the library is loaded.\n\nYou may create a shared library that refers to another library, which may be either an\narchive library or a shared library. If this second library is a shared library, this is\ncalled a \"dependent library\". The dependent library's name is recorded in the main shared\nlibrary, but it is not linked into the shared library. Instead, it is loaded when the main\nshared library is loaded. This can cause problems if you build an extension on one system\nand move it to another system where the libraries may not be located in the same place as on\nthe first system.\n\nIf the referred library is an archive library, then it is treated as a simple collection of\n.o modules (all of which must contain PIC). These modules are then linked into the shared\nlibrary.\n\nNote that it is okay to create a library which contains a dependent library that is already\nlinked into perl.\n\nSome extensions, like DBFile and Compress::Zlib use/require prebuilt libraries for the perl\nextensions/modules to work. If these libraries are built using the default configuration, it\nmight happen that you run into an error like \"invalid loader fixup\" during load phase. HP is\naware of this problem. Search the HP-UX cxx-dev forums for discussions about the subject.\nThe short answer is that everything (all libraries, everything) must be compiled with \"+z\" or\n\"+Z\" to be PIC (position independent code). (For gcc, that would be \"-fpic\" or \"-fPIC\"). In\nHP-UX 11.00 or newer the linker error message should tell the name of the offending object\nfile.\n\nA more general approach is to intervene manually, as with an example for the DBFile module,\nwhich requires SleepyCat's libdb.sl:\n\n# cd .../db-3.2.9/buildunix\n# vi Makefile\n... add +Z to all cflags to create shared objects\nCFLAGS= -c $(CPPFLAGS) +Z -Ae +O2 +Onolimit \\\n-I/usr/local/include -I/usr/include/X11R6\nCXXFLAGS= -c $(CPPFLAGS) +Z -Ae +O2 +Onolimit \\\n-I/usr/local/include -I/usr/include/X11R6\n\n# make clean\n# make\n# mkdir tmp\n# cd tmp\n# ar x ../libdb.a\n# ld -b -o libdb-3.2.sl *.o\n# mv libdb-3.2.sl /usr/local/lib\n# rm *.o\n# cd /usr/local/lib\n# rm -f libdb.sl\n# ln -s libdb-3.2.sl libdb.sl\n\n# cd .../DBFile-1.76\n# make distclean\n# perl Makefile.PL\n# make\n# make test\n# make install\n\nAs of db-4.2.x it is no longer needed to do this by hand. Sleepycat has changed the\nconfiguration process to add +z on HP-UX automatically.\n\n# cd .../db-4.2.25/buildunix\n# env CFLAGS=+DD64 LDFLAGS=+DD64 ../dist/configure\n\nshould work to generate 64bit shared libraries for HP-UX 11.00 and 11i.\n\nIt is no longer possible to link PA-RISC 1.0 shared libraries (even though the command-line\nflags are still present).\n\nPA-RISC and Itanium object files are not interchangeable. Although you may be able to use ar\nto create an archive library of PA-RISC object files on an Itanium system, you cannot link\nagainst it using an Itanium link editor.\n" }, { "name": "The HP ANSI C Compiler", "content": "When using this compiler to build Perl, you should make sure that the flag -Aa is added to\nthe cpprun and cppstdin variables in the config.sh file (though see the section on 64-bit\nperl below). If you are using a recent version of the Perl distribution, these flags are set\nautomatically.\n\nEven though HP-UX 10.20 and 11.00 are not actively maintained by HP anymore, updates for the\nHP ANSI C compiler are still available from time to time, and it might be advisable to see if\nupdates are applicable. At the moment of writing, the latests available patches for 11.00\nthat should be applied are PHSS35098, PHSS35175, PHSS35100, PHSS33036, and PHSS33902).\nIf you have a SUM account, you can use it to search for updates/patches. Enter \"ANSI\" as\nkeyword.\n" }, { "name": "The GNU C Compiler", "content": "When you are going to use the GNU C compiler (gcc), and you don't have gcc yet, you can\neither build it yourself (if you feel masochistic enough) from the sources (available from\ne.g. ) or fetch a prebuilt binary from the HP porting center\nat or from the DSPP\n(you need to be a member) at\n\n(Browse through the list, because there are often multiple versions of the same package\navailable).\n\nMost mentioned distributions are depots. H.Merijn Brand has made prebuilt gcc binaries\navailable on and/or for\nHP-UX 10.20 (only 32bit), HP-UX 11.00, HP-UX 11.11 (HP-UX 11i v1), and HP-UX 11.23 (HP-UX 11i\nv2 PA-RISC) in both 32- and 64-bit versions. For HP-UX 11.23 IPF and HP-UX 11.31 IPF depots\nare available too. The IPF versions do not need two versions of GNU gcc.\n\nOn PA-RISC you need a different compiler for 32-bit applications and for 64-bit applications.\nOn PA-RISC, 32-bit objects and 64-bit objects do not mix. Period. There is no different\nbehaviour for HP C-ANSI-C or GNU gcc. So if you require your perl binary to use 64-bit\nlibraries, like Oracle-64bit, you MUST build a 64-bit perl.\n\nBuilding a 64-bit capable gcc on PA-RISC from source is possible only when you have the HP\nC-ANSI C compiler or an already working 64-bit binary of gcc available. Best performance for\nperl is achieved with HP's native compiler.\n" }, { "name": "Using Large Files with Perl on HP-UX", "content": "Beginning with HP-UX version 10.20, files larger than 2GB (2^31 bytes) may be created and\nmanipulated. Three separate methods of doing this are available. Of these methods, the best\nmethod for Perl is to compile using the -Duselargefiles flag to Configure. This causes Perl\nto be compiled using structures and functions in which these are 64 bits wide, rather than 32\nbits wide. (Note that this will only work with HP's ANSI C compiler. If you want to compile\nPerl using gcc, you will have to get a version of the compiler that supports 64-bit\noperations. See above for where to find it.)\n\nThere are some drawbacks to this approach. One is that any extension which calls any file-\nmanipulating C function will need to be recompiled (just follow the usual \"perl Makefile.PL;\nmake; make test; make install\" procedure).\n\nThe list of functions that will need to recompiled is:\ncreat, fgetpos, fopen,\nfreopen, fsetpos, fstat,\nfstatvfs, fstatvfsdev, ftruncate,\nftw, lockf, lseek,\nlstat, mmap, nftw,\nopen, prealloc, stat,\nstatvfs, statvfsdev, tmpfile,\ntruncate, getrlimit, setrlimit\n\nAnother drawback is only valid for Perl versions before 5.6.0. This drawback is that the\nseek and tell functions (both the builtin version and POSIX module version) will not perform\ncorrectly.\n\nIt is strongly recommended that you use this flag when you run Configure. If you do not do\nthis, but later answer the question about large files when Configure asks you, you may get a\nconfiguration that cannot be compiled, or that does not function as expected.\n" }, { "name": "Threaded Perl on HP-UX", "content": "It is possible to compile a version of threaded Perl on any version of HP-UX before 10.30,\nbut it is strongly suggested that you be running on HP-UX 11.00 at least.\n\nTo compile Perl with threads, add -Dusethreads to the arguments of Configure. Verify that\nthe -DPOSIXCSOURCE=199506L compiler flag is automatically added to the list of flags.\nAlso make sure that -lpthread is listed before -lc in the list of libraries to link Perl\nwith. The hints provided for HP-UX during Configure will try very hard to get this right for\nyou.\n\nHP-UX versions before 10.30 require a separate installation of a POSIX threads library\npackage. Two examples are the HP DCE package, available on \"HP-UX Hardware Extensions 3.0,\nInstall and Core OS, Release 10.20, April 1999 (B3920-13941)\" or the Freely available PTH\npackage, available on H.Merijn's site (). The use of PTH\nwill be unsupported in perl-5.12 and up and is rather buggy in 5.11.x.\n\nIf you are going to use the HP DCE package, the library used for threading is\n/usr/lib/libcma.sl, but there have been multiple updates of that library over time. Perl will\nbuild with the first version, but it will not pass the test suite. Older Oracle versions\nmight be a compelling reason not to update that library, otherwise please find a newer\nversion in one of the following patches: PHSS19739, PHSS20608, or PHSS23672\n\nreformatted output:\n\nd3:/usr/lib 106 > what libcma-*.1\nlibcma-00000.1:\nHP DCE/9000 1.5 Module: libcma.sl (Export)\nDate: Apr 29 1996 22:11:24\nlibcma-19739.1:\nHP DCE/9000 1.5 PHSS19739-40 Module: libcma.sl (Export)\nDate: Sep 4 1999 01:59:07\nlibcma-20608.1:\nHP DCE/9000 1.5 PHSS20608 Module: libcma.1 (Export)\nDate: Dec 8 1999 18:41:23\nlibcma-23672.1:\nHP DCE/9000 1.5 PHSS23672 Module: libcma.1 (Export)\nDate: Apr 9 2001 10:01:06\nd3:/usr/lib 107 >\n\nIf you choose for the PTH package, use swinstall to install pth in the default location\n(/opt/pth), and then make symbolic links to the libraries from /usr/lib\n\n# cd /usr/lib\n# ln -s /opt/pth/lib/libpth* .\n\nFor building perl to support Oracle, it needs to be linked with libcl and libpthread. So even\nif your perl is an unthreaded build, these libraries might be required. See \"Oracle on HP-UX\"\nbelow.\n" }, { "name": "64-bit Perl on HP-UX", "content": "Beginning with HP-UX 11.00, programs compiled under HP-UX can take advantage of the LP64\nprogramming environment (LP64 means Longs and Pointers are 64 bits wide), in which scalar\nvariables will be able to hold numbers larger than 2^32 with complete precision. Perl has\nproven to be consistent and reliable in 64bit mode since 5.8.1 on all HP-UX 11.xx.\n\nAs of the date of this document, Perl is fully 64-bit compliant on HP-UX 11.00 and up for\nboth cc- and gcc builds. If you are about to build a 64-bit perl with GNU gcc, please read\nthe gcc section carefully.\n\nShould a user have the need for compiling Perl in the LP64 environment, use the -Duse64bitall\nflag to Configure. This will force Perl to be compiled in a pure LP64 environment (with the\n+DD64 flag for HP C-ANSI-C, with no additional options for GNU gcc 64-bit on PA-RISC, and\nwith -mlp64 for GNU gcc on Itanium). If you want to compile Perl using gcc, you will have to\nget a version of the compiler that supports 64-bit operations.)\n\nYou can also use the -Duse64bitint flag to Configure. Although there are some minor\ndifferences between compiling Perl with this flag versus the -Duse64bitall flag, they should\nnot be noticeable from a Perl user's perspective. When configuring -Duse64bitint using a\n64bit gcc on a pa-risc architecture, -Duse64bitint is silently promoted to -Duse64bitall.\n\nIn both cases, it is strongly recommended that you use these flags when you run Configure.\nIf you do not use do this, but later answer the questions about 64-bit numbers when Configure\nasks you, you may get a configuration that cannot be compiled, or that does not function as\nexpected.\n" }, { "name": "Oracle on HP-UX", "content": "Using perl to connect to Oracle databases through DBI and DBD::Oracle has caused a lot of\npeople many headaches. Read README.hpux in the DBD::Oracle for much more information. The\nreason to mention it here is that Oracle requires a perl built with libcl and libpthread, the\nlatter even when perl is build without threads. Building perl using all defaults, but still\nenabling to build DBD::Oracle later on can be achieved using\n\nConfigure -A prepend:libswanted='cl pthread ' ...\n\nDo not forget the space before the trailing quote.\n\nAlso note that this does not (yet) work with all configurations, it is known to fail with\n64-bit versions of GCC.\n" }, { "name": "GDBM and Threads on HP-UX", "content": "If you attempt to compile Perl with (POSIX) threads on an 11.X system and also link in the\nGDBM library, then Perl will immediately core dump when it starts up. The only workaround at\nthis point is to relink the GDBM library under 11.X, then relink it into Perl.\n\nthe error might show something like:\n\nPthread internal error: message: libcreinit() failed, file: ../pthreads/pthread.c, line:\n1096 Return Pointer is 0xc082bf33 sh: 5345 Quit(coredump)\n\nand Configure will give up.\n" }, { "name": "NFS filesystems and utime(2) on HP-UX", "content": "If you are compiling Perl on a remotely-mounted NFS filesystem, the test io/fs.t may fail on\ntest #18. This appears to be a bug in HP-UX and no fix is currently available.\n" }, { "name": "HP-UX Kernel Parameters (maxdsiz) for Compiling Perl", "content": "By default, HP-UX comes configured with a maximum data segment size of 64MB. This is too\nsmall to correctly compile Perl with the maximum optimization levels. You can increase the\nsize of the maxdsiz kernel parameter through the use of SAM.\n\nWhen using the GUI version of SAM, click on the Kernel Configuration icon, then the\nConfigurable Parameters icon. Scroll down and select the maxdsiz line. From the Actions\nmenu, select the Modify Configurable Parameter item. Insert the new formula into the\nFormula/Value box. Then follow the instructions to rebuild your kernel and reboot your\nsystem.\n\nIn general, a value of 256MB (or \"256*1024*1024\") is sufficient for Perl to compile at\nmaximum optimization.\n\nnssdelete core dump from op/pwent or op/grent\nYou may get a bus error core dump from the op/pwent or op/grent tests. If compiled with -g\nyou will see a stack trace much like the following:\n\n#0 0xc004216c in () from /usr/lib/libc.2\n#1 0xc00d7550 in nsssrcstatedestr () from /usr/lib/libc.2\n#2 0xc00d7768 in nsssrcstatedestr () from /usr/lib/libc.2\n#3 0xc00d78a8 in nssdelete () from /usr/lib/libc.2\n#4 0xc01126d8 in endpwent () from /usr/lib/libc.2\n#5 0xd1950 in Perlppepwent () from ./perl\n#6 0x94d3c in Perlrunopsstandard () from ./perl\n#7 0x23728 in Srunbody () from ./perl\n#8 0x23428 in perlrun () from ./perl\n#9 0x2005c in main () from ./perl\n\nThe key here is the \"nssdelete\" call. One workaround for this bug seems to be to create add\nto the file /etc/nsswitch.conf (at least) the following lines\n\ngroup: files\npasswd: files\n\nWhether you are using NIS does not matter. Amazingly enough, the same bug also affects\nSolaris.\n" }, { "name": "error: pasting \")\" and \"l\" does not give a valid preprocessing token", "content": "There seems to be a broken system header file in HP-UX 11.00 that breaks perl building in\n32bit mode with GNU gcc-4.x causing this error. The same file for HP-UX 11.11 (even though\nthe file is older) does not show this failure, and has the correct definition, so the best\nfix is to patch the header to match:\n\n--- /usr/include/inttypes.h 2001-04-20 18:42:14 +0200\n+++ /usr/include/inttypes.h 2000-11-14 09:00:00 +0200\n@@ -72,7 +72,7 @@\n#define UINT32C(c) CONCATU(c)\n#else /* LP64 */\n#define INT32C(c) CONCAT(c,l)\n-#define UINT32C(c) CONCAT(CONCATU(c),l)\n+#define UINT32C(c) CONCAT(c,ul)\n#endif /* LP64 */\n\n#define INT64C(c) CONCATL(c,l)\n" }, { "name": "Redeclaration of \"sendpath\" with a different storage class specifier", "content": "The following compilation warnings may happen in HP-UX releases earlier than 11.31 but are\nharmless:\n\ncc: \"/usr/include/sys/socket.h\", line 535: warning 562:\nRedeclaration of \"sendfile\" with a different storage class\nspecifier: \"sendfile\" will have internal linkage.\ncc: \"/usr/include/sys/socket.h\", line 536: warning 562:\nRedeclaration of \"sendpath\" with a different storage class\nspecifier: \"sendpath\" will have internal linkage.\n\nThey seem to be caused by broken system header files, and also other open source projects are\nseeing them. The following HP-UX patches should make the warnings go away:\n\nCR JAGae12001: PHNE27063\nWarning 562 on sys/socket.h due to redeclaration of prototypes\n\nCR JAGae16787:\nWarning 562 from socket.h sendpath/sendfile -DFILEFFSETBITS=64\n\nCR JAGae73470 (11.23)\nER: Compiling socket.h with cc -DFILEFFSETBITS=64 warning 267/562\n" } ] }, "Miscellaneous": { "content": "HP-UX 11 Y2K patch \"Y2K-1100 B.11.00.B0125 HP-UX Core OS Year 2000 Patch Bundle\" has been\nreported to break the io/fs test #18 which tests whether utime() can change timestamps. The\nY2K patch seems to break utime() so that over NFS the timestamps do not get changed (on local\nfilesystems utime() still works). This has probably been fixed on your system by now.\n", "subsections": [] }, "AUTHOR": { "content": "H.Merijn Brand Jeff Okamoto \n\nWith much assistance regarding shared libraries from Marc Sabatella.\n\n\n\nperl v5.34.0 2025-07-25 PERLHPUX(1)", "subsections": [] } } } }