1PERLHPUX(1)            Perl Programmers Reference Guide            PERLHPUX(1)
2
3
4

NAME

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

DESCRIPTION

9       This document describes various features of HP's Unix operating system
10       (HP-UX) that will affect how Perl version 5 (hereafter just Perl) is
11       compiled and/or runs.
12
13   Using perl as shipped with HP-UX
14       Application release September 2001, HP-UX 11.00 is the first to ship
15       with Perl. By the time it was perl-5.6.1 in /opt/perl. The first
16       occurrence is on CD 5012-7954 and can be installed using
17
18         swinstall -s /cdrom perl
19
20       assuming you have mounted that CD on /cdrom. In this version the
21       following modules were installed:
22
23         ActivePerl::DocTools-0.04   HTML::Parser-3.19   XML::DOM-1.25
24         Archive::Tar-0.072          HTML::Tagset-3.03   XML::Parser-2.27
25         Compress::Zlib-1.08         MIME::Base64-2.11   XML::Simple-1.05
26         Convert::ASN1-0.10          Net-1.07            XML::XPath-1.09
27         Digest::MD5-2.11            PPM-2.1.5           XML::XSLT-0.32
28         File::CounterFile-0.12      SOAP::Lite-0.46     libwww-perl-5.51
29         Font::AFM-1.18              Storable-1.011      libxml-perl-0.07
30         HTML-Tree-3.11              URI-1.11            perl-ldap-0.23
31
32       That build was a portable hppa-1.1 multithread build that supports
33       large files compiled with gcc-2.9-hppa-991112.
34
35       If you perform a new installation, then (a newer) Perl will be
36       installed automatically.  Preinstalled HP-UX systems now slao have more
37       recent versions of Perl and the updated modules.
38
39       The official (threaded) builds from HP, as they are shipped on the
40       Application DVD/CD's are available on
41       <http://www.software.hp.com/portal/swdepot/displayProductInfo.do?productNumber=PERL>
42       for both PA-RISC and IPF (Itanium Processor Family). They are built
43       with the HP ANSI-C compiler. Up till 5.8.8 that was done by
44       ActiveState.
45
46       To see what version is included on the DVD (assumed here to be mounted
47       on /cdrom), issue this command:
48
49         # swlist -s /cdrom perl
50         # perl           D.5.8.8.B  5.8.8 Perl Programming Language
51           perl.Perl5-32  D.5.8.8.B  32-bit 5.8.8 Perl Programming Language with Extensions
52           perl.Perl5-64  D.5.8.8.B  64-bit 5.8.8 Perl Programming Language with Extensions
53
54   Using perl from HP's porting centre
55       HP porting centre tries very hard to keep up with customer demand and
56       release updates from the Open Source community. Having precompiled Perl
57       binaries available is obvious.
58
59       The HP porting centres are limited in what systems they are allowed to
60       port to and they usually choose the two most recent OS versions
61       available. This means that at the moment of writing, there are only HP-
62       UX 11.11 (pa-risc 2.0) and HP-UX 11.23 (Itanium 2) ports available on
63       the porting centres.
64
65       HP has asked the porting centre to move Open Source binaries from /opt
66       to /usr/local, so binaries produced since the start of July 2002 are
67       located in /usr/local.
68
69       One of HP porting centres URL's is <http://hpux.connect.org.uk/> The
70       port currently available is built with GNU gcc.
71
72   Compiling Perl 5 on HP-UX
73       When compiling Perl, you must use an ANSI C compiler.  The C compiler
74       that ships with all HP-UX systems is a K&R compiler that should only be
75       used to build new kernels.
76
77       Perl can be compiled with either HP's ANSI C compiler or with gcc.  The
78       former is recommended, as not only can it compile Perl with no
79       difficulty, but also can take advantage of features listed later that
80       require the use of HP compiler-specific command-line flags.
81
82       If you decide to use gcc, make sure your installation is recent and
83       complete, and be sure to read the Perl INSTALL file for more gcc-
84       specific details.
85
86   PA-RISC
87       HP's HP9000 Unix systems run on HP's own Precision Architecture (PA-
88       RISC) chip.  HP-UX used to run on the Motorola MC68000 family of chips,
89       but any machine with this chip in it is quite obsolete and this
90       document will not attempt to address issues for compiling Perl on the
91       Motorola chipset.
92
93       The version of PA-RISC at the time of this document's last update is
94       2.0, which is also the last there will be. HP PA-RISC systems are
95       usually refered to with model description "HP 9000". The last CPU in
96       this series is the PA-8900.  Support for PA-RISC architectured machines
97       officially ends as shown in the following table:
98
99          PA-RISC End-of-Life Roadmap
100        +--------+----------------+----------------+-----------------+
101        | HP9000 | Superdome      | PA-8700        | Spring 2011     |
102        | 4-128  |                | PA-8800/sx1000 | Summer 2012     |
103        | cores  |                | PA-8900/sx1000 | 2014            |
104        |        |                | PA-8900/sx2000 | 2015            |
105        +--------+----------------+----------------+-----------------+
106        | HP9000 | rp7410, rp8400 | PA-8700        | Spring 2011     |
107        | 2-32   | rp7420, rp8420 | PA-8800/sx1000 | 2012            |
108        | cores  | rp7440, rp8440 | PA-8900/sx1000 | Autumn 2013     |
109        |        |                | PA-8900/sx2000 | 2015            |
110        +--------+----------------+----------------+-----------------+
111        | HP9000 | rp44x0         | PA-8700        | Spring 2011     |
112        | 1-8    |                | PA-8800/rp44x0 | 2012            |
113        | cores  |                | PA-8900/rp44x0 | 2014            |
114        +--------+----------------+----------------+-----------------+
115        | HP9000 | rp34x0         | PA-8700        | Spring 2011     |
116        | 1-4    |                | PA-8800/rp34x0 | 2012            |
117        | cores  |                | PA-8900/rp34x0 | 2014            |
118        +--------+----------------+----------------+-----------------+
119
120       From <http://www.hp.com/products1/evolution/9000/faqs.html>
121
122        The last order date for HP 9000 systems was December 31, 2008.
123
124       A complete list of models at the time the OS was built is in the file
125       /usr/sam/lib/mo/sched.models. The first column corresponds to the last
126       part of the output of the "model" command.  The second column is the
127       PA-RISC version and the third column is the exact chip type used.
128       (Start browsing at the bottom to prevent confusion ;-)
129
130         # model
131         9000/800/L1000-44
132         # grep L1000-44 /usr/sam/lib/mo/sched.models
133         L1000-44        2.0     PA8500
134
135   Portability Between PA-RISC Versions
136       An executable compiled on a PA-RISC 2.0 platform will not execute on a
137       PA-RISC 1.1 platform, even if they are running the same version of HP-
138       UX.  If you are building Perl on a PA-RISC 2.0 platform and want that
139       Perl to also run on a PA-RISC 1.1, the compiler flags +DAportable and
140       +DS32 should be used.
141
142       It is no longer possible to compile PA-RISC 1.0 executables on either
143       the PA-RISC 1.1 or 2.0 platforms.  The command-line flags are accepted,
144       but the resulting executable will not run when transferred to a PA-RISC
145       1.0 system.
146
147   PA-RISC 1.0
148       The original version of PA-RISC, HP no longer sells any system with
149       this chip.
150
151       The following systems contained PA-RISC 1.0 chips:
152
153         600, 635, 645, 808, 815, 822, 825, 832, 834, 835, 840, 842, 845, 850,
154         852, 855, 860, 865, 870, 890
155
156   PA-RISC 1.1
157       An upgrade to the PA-RISC design, it shipped for many years in many
158       different system.
159
160       The following systems contain with PA-RISC 1.1 chips:
161
162         705, 710, 712, 715, 720, 722, 725, 728, 730, 735, 742, 743, 744, 745,
163         747, 750, 755, 770, 777, 778, 779, 800, 801, 803, 806, 807, 809, 811,
164         813, 816, 817, 819, 821, 826, 827, 829, 831, 837, 839, 841, 847, 849,
165         851, 856, 857, 859, 867, 869, 877, 887, 891, 892, 897, A180, A180C,
166         B115, B120, B132L, B132L+, B160L, B180L, C100, C110, C115, C120,
167         C160L, D200, D210, D220, D230, D250, D260, D310, D320, D330, D350,
168         D360, D410, DX0, DX5, DXO, E25, E35, E45, E55, F10, F20, F30, G30,
169         G40, G50, G60, G70, H20, H30, H40, H50, H60, H70, I30, I40, I50, I60,
170         I70, J200, J210, J210XC, K100, K200, K210, K220, K230, K400, K410,
171         K420, S700i, S715, S744, S760, T500, T520
172
173   PA-RISC 2.0
174       The most recent upgrade to the PA-RISC design, it added support for
175       64-bit integer data.
176
177       As of the date of this document's last update, the following systems
178       contain PA-RISC 2.0 chips:
179
180         700, 780, 781, 782, 783, 785, 802, 804, 810, 820, 861, 871, 879, 889,
181         893, 895, 896, 898, 899, A400, A500, B1000, B2000, C130, C140, C160,
182         C180, C180+, C180-XP, C200+, C400+, C3000, C360, C3600, CB260, D270,
183         D280, D370, D380, D390, D650, J220, J2240, J280, J282, J400, J410,
184         J5000, J5500XM, J5600, J7000, J7600, K250, K260, K260-EG, K270, K360,
185         K370, K380, K450, K460, K460-EG, K460-XP, K470, K570, K580, L1000,
186         L2000, L3000, N4000, R380, R390, SD16000, SD32000, SD64000, T540,
187         T600, V2000, V2200, V2250, V2500, V2600
188
189       Just before HP took over Compaq, some systems were renamed. the link
190       that contained the explanation is dead, so here's a short summary:
191
192         HP 9000 A-Class servers, now renamed HP Server rp2400 series.
193         HP 9000 L-Class servers, now renamed HP Server rp5400 series.
194         HP 9000 N-Class servers, now renamed HP Server rp7400.
195
196         rp2400, rp2405, rp2430, rp2450, rp2470, rp3410, rp3440, rp4410,
197         rp4440, rp5400, rp5405, rp5430, rp5450, rp5470, rp7400, rp7405,
198         rp7410, rp7420, rp7440, rp8400, rp8420, rp8440, Superdome
199
200       The current naming convention is:
201
202         aadddd
203         ||||`+- 00 - 99 relative capacity & newness (upgrades, etc.)
204         |||`--- unique number for each architecture to ensure different
205         |||     systems do not have the same numbering across
206         |||     architectures
207         ||`---- 1 - 9 identifies family and/or relative positioning
208         ||
209         |`----- c = ia32 (cisc)
210         |       p = pa-risc
211         |       x = ia-64 (Itanium & Itanium 2)
212         |       h = housing
213         `------ t = tower
214                 r = rack optimized
215                 s = super scalable
216                 b = blade
217                 sa = appliance
218
219   Itanium Processor Family (IPF) and HP-UX
220       HP-UX also runs on the new Itanium processor.  This requires the use of
221       a different version of HP-UX (currently 11.23 or 11i v2), and with the
222       exception of a few differences detailed below and in later sections,
223       Perl should compile with no problems.
224
225       Although PA-RISC binaries can run on Itanium systems, you should not
226       attempt to use a PA-RISC version of Perl on an Itanium system.  This is
227       because shared libraries created on an Itanium system cannot be loaded
228       while running a PA-RISC executable.
229
230       HP Itanium 2 systems are usually refered to with model description "HP
231       Integrity".
232
233   Itanium, Itanium 2 & Madison 6
234       HP also ships servers with the 128-bit Itanium processor(s). The cx26x0
235       is told to have Madison 6. As of the date of this document's last
236       update, the following systems contain Itanium or Itanium 2 chips (this
237       is likely to be out of date):
238
239         BL60p, BL860c, BL870c, cx2600, cx2620, rx1600, rx1620, rx2600,
240         rx2600hptc, rx2620, rx2660, rx3600, rx4610, rx4640, rx5670,
241         rx6600, rx7420, rx7620, rx7640, rx8420, rx8620, rx8640, rx9610,
242         sx1000, sx2000
243
244       To see all about your machine, type
245
246         # model
247         ia64 hp server rx2600
248         # /usr/contrib/bin/machinfo
249
250   HP-UX versions
251       Not all architectures (PA = PA-RISC, IPF = Itanium Processor Family)
252       support all versions of HP-UX, here is a short list
253
254         HP-UX version  Kernel  Architecture
255         -------------  ------  ------------
256         10.20          32 bit  PA
257         11.00          32/64   PA
258         11.11  11i v1  32/64   PA
259         11.22  11i v2     64        IPF
260         11.23  11i v2     64   PA & IPF
261         11.31  11i v3     64   PA & IPF
262
263       See for the full list of hardware/OS support and expected end-of-life
264       <http://www.hp.com/go/hpuxservermatrix>
265
266   Building Dynamic Extensions on HP-UX
267       HP-UX supports dynamically loadable libraries (shared libraries).
268       Shared libraries end with the suffix .sl.  On Itanium systems, they end
269       with the suffix .so.
270
271       Shared libraries created on a platform using a particular PA-RISC
272       version are not usable on platforms using an earlier PA-RISC version by
273       default.  However, this backwards compatibility may be enabled using
274       the same +DAportable compiler flag (with the same PA-RISC 1.0 caveat
275       mentioned above).
276
277       Shared libraries created on an Itanium platform cannot be loaded on a
278       PA-RISC platform.  Shared libraries created on a PA-RISC platform can
279       only be loaded on an Itanium platform if it is a PA-RISC executable
280       that is attempting to load the PA-RISC library.  A PA-RISC shared
281       library cannot be loaded into an Itanium executable nor vice-versa.
282
283       To create a shared library, the following steps must be performed:
284
285         1. Compile source modules with +z or +Z flag to create a .o module
286            which contains Position-Independent Code (PIC).  The linker will
287            tell you in the next step if +Z was needed.
288            (For gcc, the appropriate flag is -fpic or -fPIC.)
289
290         2. Link the shared library using the -b flag.  If the code calls
291            any functions in other system libraries (e.g., libm), it must
292            be included on this line.
293
294       (Note that these steps are usually handled automatically by the
295       extension's Makefile).
296
297       If these dependent libraries are not listed at shared library creation
298       time, you will get fatal "Unresolved symbol" errors at run time when
299       the library is loaded.
300
301       You may create a shared library that refers to another library, which
302       may be either an archive library or a shared library.  If this second
303       library is a shared library, this is called a "dependent library".  The
304       dependent library's name is recorded in the main shared library, but it
305       is not linked into the shared library.  Instead, it is loaded when the
306       main shared library is loaded.  This can cause problems if you build an
307       extension on one system and move it to another system where the
308       libraries may not be located in the same place as on the first system.
309
310       If the referred library is an archive library, then it is treated as a
311       simple collection of .o modules (all of which must contain PIC).  These
312       modules are then linked into the shared library.
313
314       Note that it is okay to create a library which contains a dependent
315       library that is already linked into perl.
316
317       Some extensions, like DB_File and Compress::Zlib use/require prebuilt
318       libraries for the perl extensions/modules to work. If these libraries
319       are built using the default configuration, it might happen that you run
320       into an error like "invalid loader fixup" during load phase.  HP is
321       aware of this problem.  Search the HP-UX cxx-dev forums for discussions
322       about the subject.  The short answer is that everything (all libraries,
323       everything) must be compiled with "+z" or "+Z" to be PIC (position
324       independent code).  (For gcc, that would be "-fpic" or "-fPIC").  In
325       HP-UX 11.00 or newer the linker error message should tell the name of
326       the offending object file.
327
328       A more general approach is to intervene manually, as with an example
329       for the DB_File module, which requires SleepyCat's libdb.sl:
330
331         # cd .../db-3.2.9/build_unix
332         # vi Makefile
333         ... add +Z to all cflags to create shared objects
334         CFLAGS=         -c $(CPPFLAGS) +Z -Ae +O2 +Onolimit \
335                         -I/usr/local/include -I/usr/include/X11R6
336         CXXFLAGS=       -c $(CPPFLAGS) +Z -Ae +O2 +Onolimit \
337                         -I/usr/local/include -I/usr/include/X11R6
338
339         # make clean
340         # make
341         # mkdir tmp
342         # cd tmp
343         # ar x ../libdb.a
344         # ld -b -o libdb-3.2.sl *.o
345         # mv libdb-3.2.sl /usr/local/lib
346         # rm *.o
347         # cd /usr/local/lib
348         # rm -f libdb.sl
349         # ln -s libdb-3.2.sl libdb.sl
350
351         # cd .../DB_File-1.76
352         # make distclean
353         # perl Makefile.PL
354         # make
355         # make test
356         # make install
357
358       As of db-4.2.x it is no longer needed to do this by hand. Sleepycat has
359       changed the configuration process to add +z on HP-UX automatically.
360
361         # cd .../db-4.2.25/build_unix
362         # env CFLAGS=+DD64 LDFLAGS=+DD64 ../dist/configure
363
364       should work to generate 64bit shared libraries for HP-UX 11.00 and 11i.
365
366       It is no longer possible to link PA-RISC 1.0 shared libraries (even
367       though the command-line flags are still present).
368
369       PA-RISC and Itanium object files are not interchangeable.  Although you
370       may be able to use ar to create an archive library of PA-RISC object
371       files on an Itanium system, you cannot link against it using an Itanium
372       link editor.
373
374   The HP ANSI C Compiler
375       When using this compiler to build Perl, you should make sure that the
376       flag -Aa is added to the cpprun and cppstdin variables in the config.sh
377       file (though see the section on 64-bit perl below). If you are using a
378       recent version of the Perl distribution, these flags are set
379       automatically.
380
381       Even though HP-UX 10.20 and 11.00 are not actively maintained by HP
382       anymore, updates for the HP ANSI C compiler are still available from
383       time to time, and it might be advisable to see if updates are
384       applicable.  At the moment of writing, the latests available patches
385       for 11.00 that should be applied are PHSS_35098, PHSS_35175,
386       PHSS_35100, PHSS_33036, and PHSS_33902). If you have a SUM account, you
387       can use it to search for updates/patches. Enter "ANSI" as keyword.
388
389   The GNU C Compiler
390       When you are going to use the GNU C compiler (gcc), and you don't have
391       gcc yet, you can either build it yourself from the sources (available
392       from e.g. <http://gcc.gnu.org/mirrors.html>) or fetch a prebuilt binary
393       from the HP porting center. gcc prebuilds can be fetched from
394       <http://h21007.www2.hp.com/dspp/tech/tech_TechSoftwareDetailPage_IDX/1,1703,547,00.html>
395       (Browse through the list, because there are often multiple versions of
396       the same package available).
397
398       Above mentioned distributions are depots. H.Merijn Brand has made
399       prebuilt gcc binaries available on
400       <http://mirrors.develooper.com/hpux/> and/or
401       <http://www.cmve.net/~merijn/> for HP-UX 10.20, HP-UX 11.00, HP-UX
402       11.11 (HP-UX 11i v1), and HP-UX 11.23 (HP-UX 11i v2) in both 32- and
403       64-bit versions. These are bzipped tar archives that also include
404       recent GNU binutils and GNU gdb.  Read the instructions on that page to
405       rebuild gcc using itself.
406
407       On PA-RISC you need a different compiler for 32-bit applications and
408       for 64-bit applications. On PA-RISC, 32-bit objects and 64-bit objects
409       do not mix. Period. There is no different behaviour for HP C-ANSI-C or
410       GNU gcc. So if you require your perl binary to use 64-bit libraries,
411       like Oracle-64bit, you MUST build a 64-bit perl.
412
413       Building a 64-bit capable gcc on PA-RISC from source is possible only
414       when you have the HP C-ANSI C compiler or an already working 64-bit
415       binary of gcc available. Best performance for perl is achieved with
416       HP's native compiler.
417
418   Using Large Files with Perl on HP-UX
419       Beginning with HP-UX version 10.20, files larger than 2GB (2^31 bytes)
420       may be created and manipulated.  Three separate methods of doing this
421       are available.  Of these methods, the best method for Perl is to
422       compile using the -Duselargefiles flag to Configure.  This causes Perl
423       to be compiled using structures and functions in which these are 64
424       bits wide, rather than 32 bits wide.  (Note that this will only work
425       with HP's ANSI C compiler.  If you want to compile Perl using gcc, you
426       will have to get a version of the compiler that supports 64-bit
427       operations. See above for where to find it.)
428
429       There are some drawbacks to this approach.  One is that any extension
430       which calls any file-manipulating C function will need to be recompiled
431       (just follow the usual "perl Makefile.PL; make; make test; make
432       install" procedure).
433
434       The list of functions that will need to recompiled is:
435         creat,          fgetpos,        fopen,
436         freopen,        fsetpos,        fstat,
437         fstatvfs,       fstatvfsdev,    ftruncate,
438         ftw,            lockf,          lseek,
439         lstat,          mmap,           nftw,
440         open,           prealloc,       stat,
441         statvfs,        statvfsdev,     tmpfile,
442         truncate,       getrlimit,      setrlimit
443
444       Another drawback is only valid for Perl versions before 5.6.0.  This
445       drawback is that the seek and tell functions (both the builtin version
446       and POSIX module version) will not perform correctly.
447
448       It is strongly recommended that you use this flag when you run
449       Configure.  If you do not do this, but later answer the question about
450       large files when Configure asks you, you may get a configuration that
451       cannot be compiled, or that does not function as expected.
452
453   Threaded Perl on HP-UX
454       It is possible to compile a version of threaded Perl on any version of
455       HP-UX before 10.30, but it is strongly suggested that you be running on
456       HP-UX 11.00 at least.
457
458       To compile Perl with threads, add -Dusethreads to the arguments of
459       Configure.  Verify that the -D_POSIX_C_SOURCE=199506L compiler flag is
460       automatically added to the list of flags.  Also make sure that
461       -lpthread is listed before -lc in the list of libraries to link Perl
462       with. The hints provided for HP-UX during Configure will try very hard
463       to get this right for you.
464
465       HP-UX versions before 10.30 require a separate installation of a POSIX
466       threads library package. Two examples are the HP DCE package, available
467       on "HP-UX Hardware Extensions 3.0, Install and Core OS, Release 10.20,
468       April 1999 (B3920-13941)" or the Freely available PTH package,
469       available on H.Merijn's site (<http://mirrors.develooper.com/hpux/>).
470       The use of PTH will be unsupported in perl-5.12 and up and is rather
471       buggy in 5.11.x.
472
473       If you are going to use the HP DCE package, the library used for
474       threading is /usr/lib/libcma.sl, but there have been multiple updates
475       of that library over time. Perl will build with the first version, but
476       it will not pass the test suite. Older Oracle versions might be a
477       compelling reason not to update that library, otherwise please find a
478       newer version in one of the following patches: PHSS_19739, PHSS_20608,
479       or PHSS_23672
480
481       reformatted output:
482
483         d3:/usr/lib 106 > what libcma-*.1
484         libcma-00000.1:
485            HP DCE/9000 1.5               Module: libcma.sl (Export)
486                                          Date: Apr 29 1996 22:11:24
487         libcma-19739.1:
488            HP DCE/9000 1.5 PHSS_19739-40 Module: libcma.sl (Export)
489                                          Date: Sep  4 1999 01:59:07
490         libcma-20608.1:
491            HP DCE/9000 1.5 PHSS_20608    Module: libcma.1 (Export)
492                                          Date: Dec  8 1999 18:41:23
493         libcma-23672.1:
494            HP DCE/9000 1.5 PHSS_23672    Module: libcma.1 (Export)
495                                          Date: Apr  9 2001 10:01:06
496         d3:/usr/lib 107 >
497
498       If you choose for the PTH package, use swinstall to install pth in the
499       default location (/opt/pth), and then make symbolic links to the
500       libraries from /usr/lib
501
502         # cd /usr/lib
503         # ln -s /opt/pth/lib/libpth* .
504
505       For building perl to support Oracle, it needs to be linked with libcl
506       and libpthread. So even if your perl is an unthreaded build, these
507       libraries might be required. See "Oracle on HP-UX" below.
508
509   64-bit Perl on HP-UX
510       Beginning with HP-UX 11.00, programs compiled under HP-UX can take
511       advantage of the LP64 programming environment (LP64 means Longs and
512       Pointers are 64 bits wide), in which scalar variables will be able to
513       hold numbers larger than 2^32 with complete precision.  Perl has proven
514       to be consistent and reliable in 64bit mode since 5.8.1 on all HP-UX
515       11.xx.
516
517       As of the date of this document, Perl is fully 64-bit compliant on HP-
518       UX 11.00 and up for both cc- and gcc builds. If you are about to build
519       a 64-bit perl with GNU gcc, please read the gcc section carefully.
520
521       Should a user have the need for compiling Perl in the LP64 environment,
522       use the -Duse64bitall flag to Configure.  This will force Perl to be
523       compiled in a pure LP64 environment (with the +DD64 flag for HP C-ANSI-
524       C, with no additional options for GNU gcc 64-bit on PA-RISC, and with
525       -mlp64 for GNU gcc on Itanium).  If you want to compile Perl using gcc,
526       you will have to get a version of the compiler that supports 64-bit
527       operations.)
528
529       You can also use the -Duse64bitint flag to Configure.  Although there
530       are some minor differences between compiling Perl with this flag versus
531       the -Duse64bitall flag, they should not be noticeable from a Perl
532       user's perspective. When configuring -Duse64bitint using a 64bit gcc on
533       a pa-risc architecture, -Duse64bitint is silently promoted to
534       -Duse64bitall.
535
536       In both cases, it is strongly recommended that you use these flags when
537       you run Configure.  If you do not use do this, but later answer the
538       questions about 64-bit numbers when Configure asks you, you may get a
539       configuration that cannot be compiled, or that does not function as
540       expected.
541
542   Oracle on HP-UX
543       Using perl to connect to Oracle databases through DBI and DBD::Oracle
544       has caused a lot of people many headaches. Read README.hpux in the
545       DBD::Oracle for much more information. The reason to mention it here is
546       that Oracle requires a perl built with libcl and libpthread, the latter
547       even when perl is build without threads. Building perl using all
548       defaults, but still enabling to build DBD::Oracle later on can be
549       achieved using
550
551         Configure -A prepend:libswanted='cl pthread ' ...
552
553       Do not forget the space before the trailing quote.
554
555       Also note that this does not (yet) work with all configurations, it is
556       known to fail with 64-bit versions of GCC.
557
558   GDBM and Threads on HP-UX
559       If you attempt to compile Perl with (POSIX) threads on an 11.X system
560       and also link in the GDBM library, then Perl will immediately core dump
561       when it starts up.  The only workaround at this point is to relink the
562       GDBM library under 11.X, then relink it into Perl.
563
564       the error might show something like:
565
566       Pthread internal error: message: __libc_reinit() failed, file:
567       ../pthreads/pthread.c, line: 1096 Return Pointer is 0xc082bf33 sh: 5345
568       Quit(coredump)
569
570       and Configure will give up.
571
572   NFS filesystems and utime(2) on HP-UX
573       If you are compiling Perl on a remotely-mounted NFS filesystem, the
574       test io/fs.t may fail on test #18.  This appears to be a bug in HP-UX
575       and no fix is currently available.
576
577   HP-UX Kernel Parameters (maxdsiz) for Compiling Perl
578       By default, HP-UX comes configured with a maximum data segment size of
579       64MB.  This is too small to correctly compile Perl with the maximum
580       optimization levels.  You can increase the size of the maxdsiz kernel
581       parameter through the use of SAM.
582
583       When using the GUI version of SAM, click on the Kernel Configuration
584       icon, then the Configurable Parameters icon.  Scroll down and select
585       the maxdsiz line.  From the Actions menu, select the Modify
586       Configurable Parameter item.  Insert the new formula into the
587       Formula/Value box.  Then follow the instructions to rebuild your kernel
588       and reboot your system.
589
590       In general, a value of 256MB (or "256*1024*1024") is sufficient for
591       Perl to compile at maximum optimization.
592

nss_delete core dump from op/pwent or op/grent

594       You may get a bus error core dump from the op/pwent or op/grent tests.
595       If compiled with -g you will see a stack trace much like the following:
596
597         #0  0xc004216c in  () from /usr/lib/libc.2
598         #1  0xc00d7550 in __nss_src_state_destr () from /usr/lib/libc.2
599         #2  0xc00d7768 in __nss_src_state_destr () from /usr/lib/libc.2
600         #3  0xc00d78a8 in nss_delete () from /usr/lib/libc.2
601         #4  0xc01126d8 in endpwent () from /usr/lib/libc.2
602         #5  0xd1950 in Perl_pp_epwent () from ./perl
603         #6  0x94d3c in Perl_runops_standard () from ./perl
604         #7  0x23728 in S_run_body () from ./perl
605         #8  0x23428 in perl_run () from ./perl
606         #9  0x2005c in main () from ./perl
607
608       The key here is the "nss_delete" call.  One workaround for this bug
609       seems to be to create add to the file /etc/nsswitch.conf (at least) the
610       following lines
611
612         group: files
613         passwd: files
614
615       Whether you are using NIS does not matter.  Amazingly enough, the same
616       bug also affects Solaris.
617

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

619       There seems to be a broken system header file in HP-UX 11.00 that
620       breaks perl building in 32bit mode with GNU gcc-4.x causing this error.
621       The same file for HP-UX 11.11 (even though the file is older) does not
622       show this failure, and has the correct definition, so the best fix is
623       to patch the header to match:
624
625        --- /usr/include/inttypes.h  2001-04-20 18:42:14 +0200
626        +++ /usr/include/inttypes.h  2000-11-14 09:00:00 +0200
627        @@ -72,7 +72,7 @@
628         #define UINT32_C(__c)                   __CONCAT_U__(__c)
629         #else /* __LP64 */
630         #define INT32_C(__c)                    __CONCAT__(__c,l)
631        -#define UINT32_C(__c)                   __CONCAT__(__CONCAT_U__(__c),l)
632        +#define UINT32_C(__c)                   __CONCAT__(__c,ul)
633         #endif /* __LP64 */
634
635         #define INT64_C(__c)                    __CONCAT_L__(__c,l)
636

Miscellaneous

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

AUTHOR

646       H.Merijn Brand <h.m.brand@xs4all.nl> Jeff Okamoto <okamoto@corp.hp.com>
647
648       With much assistance regarding shared libraries from Marc Sabatella.
649
650
651
652perl v5.16.3                      2013-03-04                       PERLHPUX(1)
Impressum