3 If you read this file _as_is_, just ignore the funny characters you see.
4 It is written in the POD format (see pod/perlpod.pod) which is specially
5 designed to be readable as is.
9 perlhpux - Perl version 5 on Hewlett-Packard Unix (HP-UX) systems
13 This document describes various features of HP's Unix operating system
14 (HP-UX) that will affect how Perl version 5 (hereafter just Perl) is
17 =head2 Using perl as shipped with HP-UX
19 Application release September 2001, HP-UX 11.00 is the first to ship
20 with Perl. By the time it was perl-5.6.1 in /opt/perl. The first
21 occurrence is on CD 5012-7954 and can be installed using
23 swinstall -s /cdrom perl
25 assuming you have mounted that CD on /cdrom.
27 That build was a portable hppa-1.1 multithread build that supports large
28 files compiled with gcc-2.9-hppa-991112.
30 If you perform a new installation, then (a newer) Perl will be installed
31 automatically. Pre-installed HP-UX systems now have more recent versions
32 of Perl and the updated modules.
34 The official (threaded) builds from HP, as they are shipped on the
35 Application DVD/CD's are available on
36 L<http://www.software.hp.com/portal/swdepot/displayProductInfo.do?productNumber=PERL>
37 for both PA-RISC and IPF (Itanium Processor Family). They are built
38 with the HP ANSI-C compiler. Up till 5.8.8 that was done by ActiveState.
40 To see what version is included on the DVD (assumed here to be mounted
41 on /cdrom), issue this command:
43 # swlist -s /cdrom perl
44 # perl D.5.8.8.B 5.8.8 Perl Programming Language
45 perl.Perl5-32 D.5.8.8.B 32-bit 5.8.8 Perl Programming Language
47 perl.Perl5-64 D.5.8.8.B 64-bit 5.8.8 Perl Programming Language
50 To see what is installed on your system:
53 # perl E.5.8.8.J Perl Programming Language
54 # perl.Perl5-32 E.5.8.8.J 32-bit Perl Programming Language
56 perl.Perl5-32.PERL-MAN E.5.8.8.J 32-bit Perl Man Pages for IA
57 perl.Perl5-32.PERL-RUN E.5.8.8.J 32-bit Perl Binaries for IA
58 # perl.Perl5-64 E.5.8.8.J 64-bit Perl Programming Language
60 perl.Perl5-64.PERL-MAN E.5.8.8.J 64-bit Perl Man Pages for IA
61 perl.Perl5-64.PERL-RUN E.5.8.8.J 64-bit Perl Binaries for IA
63 =head2 Using perl from HP's porting centre
65 HP porting centre tries to keep up with customer demand and release
66 updates from the Open Source community. Having precompiled Perl binaries
67 available is obvious, though "up-to-date" is something relative. At the
68 moment of writing perl-5.10.1 and 5.28.0 were available.
70 The HP porting centres are limited in what systems they are allowed
71 to port to and they usually choose the two most recent OS versions
74 HP has asked the porting centre to move Open Source binaries
75 from /opt to /usr/local, so binaries produced since the start
76 of July 2002 are located in /usr/local.
78 One of HP porting centres URL's is L<http://hpux.connect.org.uk/>
79 The port currently available is built with GNU gcc. As porting modern
80 GNU gcc is extremely hard on HP-UX, they are stuck at version gcc-4.2.3.
82 =head2 Other prebuilt perl binaries
84 To get more perl depots for the whole range of HP-UX, visit
85 H.Merijn Brand's site at L<http://mirrors.develooper.com/hpux/#Perl>.
86 Carefully read the notes to see if the available versions suit your needs.
88 =head2 Compiling Perl 5 on HP-UX
90 When compiling Perl, you must use an ANSI C compiler. The C compiler
91 that ships with all HP-UX systems is a K&R compiler that should only be
92 used to build new kernels.
94 Perl can be compiled with either HP's ANSI C compiler or with gcc. The
95 former is recommended, as not only can it compile Perl with no
96 difficulty, but also can take advantage of features listed later that
97 require the use of HP compiler-specific command-line flags.
99 If you decide to use gcc, make sure your installation is recent and
100 complete, and be sure to read the Perl INSTALL file for more gcc-specific
105 The last and final version of PA-RISC is 2.0, HP no longer sells any
106 system with these CPU's.
108 HP's HP9000 Unix systems run on HP's own Precision Architecture
109 (PA-RISC) chip. HP-UX used to run on the Motorola MC68000 family of
110 chips, but any machine with this chip in it is quite obsolete and this
111 document will not attempt to address issues for compiling Perl on the
112 Motorola chipset. Even though PA-RISC hardware is not sold anymore, a
113 lot of machines still running on these CPU's can be found in the wild.
115 The last order date for HP 9000 systems was December 31, 2008.
117 HP PA-RISC systems are usually referred to with model description "HP 9000".
118 The last CPU in this series is the PA-8900. Support for PA-RISC
119 architectured machines officially ended as shown in the following table:
121 PA-RISC End-of-Life Roadmap
122 +--------+----------------+----------------+-----------------+
123 | HP9000 | Superdome | PA-8700 | Spring 2011 |
124 | 4-128 | | PA-8800/sx1000 | Summer 2012 |
125 | cores | | PA-8900/sx1000 | 2014 |
126 | | | PA-8900/sx2000 | 2015 |
127 +--------+----------------+----------------+-----------------+
128 | HP9000 | rp7410, rp8400 | PA-8700 | Spring 2011 |
129 | 2-32 | rp7420, rp8420 | PA-8800/sx1000 | 2012 |
130 | cores | rp7440, rp8440 | PA-8900/sx1000 | Autumn 2013 |
131 | | | PA-8900/sx2000 | 2015 |
132 +--------+----------------+----------------+-----------------+
133 | HP9000 | rp44x0 | PA-8700 | Spring 2011 |
134 | 1-8 | | PA-8800/rp44x0 | 2012 |
135 | cores | | PA-8900/rp44x0 | 2014 |
136 +--------+----------------+----------------+-----------------+
137 | HP9000 | rp34x0 | PA-8700 | Spring 2011 |
138 | 1-4 | | PA-8800/rp34x0 | 2012 |
139 | cores | | PA-8900/rp34x0 | 2014 |
140 +--------+----------------+----------------+-----------------+
142 A complete list of models at the time the OS was built is in the file
143 /usr/sam/lib/mo/sched.models. The first column corresponds to the last
144 part of the output of the "model" command. The second column is the
145 PA-RISC version and the third column is the exact chip type used.
146 (Start browsing at the bottom to prevent confusion ;-)
150 # grep L1000-44 /usr/sam/lib/mo/sched.models
155 The original version of PA-RISC, HP no longer sells any system with this chip.
157 The following systems contained PA-RISC 1.0 chips:
159 600, 635, 645, 808, 815, 822, 825, 832, 834, 835, 840, 842, 845, 850,
160 852, 855, 860, 865, 870, 890
164 An upgrade to the PA-RISC design, it shipped for many years in many different
167 The following systems contain with PA-RISC 1.1 chips:
169 705, 710, 712, 715, 720, 722, 725, 728, 730, 735, 742, 743, 744, 745,
170 747, 750, 755, 770, 777, 778, 779, 800, 801, 803, 806, 807, 809, 811,
171 813, 816, 817, 819, 821, 826, 827, 829, 831, 837, 839, 841, 847, 849,
172 851, 856, 857, 859, 867, 869, 877, 887, 891, 892, 897, A180, A180C,
173 B115, B120, B132L, B132L+, B160L, B180L, C100, C110, C115, C120,
174 C160L, D200, D210, D220, D230, D250, D260, D310, D320, D330, D350,
175 D360, D410, DX0, DX5, DXO, E25, E35, E45, E55, F10, F20, F30, G30,
176 G40, G50, G60, G70, H20, H30, H40, H50, H60, H70, I30, I40, I50, I60,
177 I70, J200, J210, J210XC, K100, K200, K210, K220, K230, K400, K410,
178 K420, S700i, S715, S744, S760, T500, T520
182 The most recent upgrade to the PA-RISC design, it added support for
185 As of the date of this document's last update, the following systems
186 contain PA-RISC 2.0 chips:
188 700, 780, 781, 782, 783, 785, 802, 804, 810, 820, 861, 871, 879, 889,
189 893, 895, 896, 898, 899, A400, A500, B1000, B2000, C130, C140, C160,
190 C180, C180+, C180-XP, C200+, C400+, C3000, C360, C3600, CB260, D270,
191 D280, D370, D380, D390, D650, J220, J2240, J280, J282, J400, J410,
192 J5000, J5500XM, J5600, J7000, J7600, K250, K260, K260-EG, K270, K360,
193 K370, K380, K450, K460, K460-EG, K460-XP, K470, K570, K580, L1000,
194 L2000, L3000, N4000, R380, R390, SD16000, SD32000, SD64000, T540,
195 T600, V2000, V2200, V2250, V2500, V2600
197 Just before HP took over Compaq, some systems were renamed. the link
198 that contained the explanation is dead, so here's a short summary:
200 HP 9000 A-Class servers, now renamed HP Server rp2400 series.
201 HP 9000 L-Class servers, now renamed HP Server rp5400 series.
202 HP 9000 N-Class servers, now renamed HP Server rp7400.
204 rp2400, rp2405, rp2430, rp2450, rp2470, rp3410, rp3440, rp4410,
205 rp4440, rp5400, rp5405, rp5430, rp5450, rp5470, rp7400, rp7405,
206 rp7410, rp7420, rp7440, rp8400, rp8420, rp8440, Superdome
208 The current naming convention is:
211 ||||`+- 00 - 99 relative capacity & newness (upgrades, etc.)
212 |||`--- unique number for each architecture to ensure different
213 ||| systems do not have the same numbering across
215 ||`---- 1 - 9 identifies family and/or relative positioning
217 |`----- c = ia32 (cisc)
219 | x = ia-64 (Itanium & Itanium 2)
227 =head2 Portability Between PA-RISC Versions
229 An executable compiled on a PA-RISC 2.0 platform will not execute on a
230 PA-RISC 1.1 platform, even if they are running the same version of
231 HP-UX. If you are building Perl on a PA-RISC 2.0 platform and want that
232 Perl to also run on a PA-RISC 1.1, the compiler flags +DAportable and
233 +DS32 should be used.
235 It is no longer possible to compile PA-RISC 1.0 executables on either
236 the PA-RISC 1.1 or 2.0 platforms. The command-line flags are accepted,
237 but the resulting executable will not run when transferred to a PA-RISC
240 =head2 Itanium Processor Family (IPF) and HP-UX
242 HP-UX also runs on the newer Itanium processor. This requires the use
243 of HP-UX version 11.23 (11i v2) or 11.31 (11i v3), and with the exception
244 of a few differences detailed below and in later sections, Perl should
245 compile with no problems.
247 Although PA-RISC binaries can run on Itanium systems, you should not
248 attempt to use a PA-RISC version of Perl on an Itanium system. This is
249 because shared libraries created on an Itanium system cannot be loaded
250 while running a PA-RISC executable.
252 HP Itanium 2 systems are usually referred to with model description
255 =head2 Itanium, Itanium 2 & Madison 6
257 HP also ships servers with the 128-bit Itanium processor(s). The cx26x0
258 is told to have Madison 6. As of the date of this document's last update,
259 the following systems contain Itanium or Itanium 2 chips (this is likely
262 BL60p, BL860c, BL870c, BL890c, cx2600, cx2620, rx1600, rx1620, rx2600,
263 rx2600hptc, rx2620, rx2660, rx2800, rx3600, rx4610, rx4640, rx5670,
264 rx6600, rx7420, rx7620, rx7640, rx8420, rx8620, rx8640, rx9610,
267 To see all about your machine, type
270 ia64 hp server rx2600
271 # /usr/contrib/bin/machinfo
273 =head2 HP-UX versions
275 Not all architectures (PA = PA-RISC, IPF = Itanium Processor Family)
276 support all versions of HP-UX, here is a short list
278 HP-UX version Kernel Architecture End-of-factory support
279 ------------- ------ ------------ ----------------------------------
280 10.20 32 bit PA 30-Jun-2003
281 11.00 32/64 PA 31-Dec-2006
282 11.11 11i v1 32/64 PA 31-Dec-2015
283 11.22 11i v2 64 IPF 30-Apr-2004
284 11.23 11i v2 64 PA & IPF 31-Dec-2015
285 11.31 11i v3 64 PA & IPF 31-Dec-2020 (PA) 31-Dec-2025 (IPF)
287 See for the full list of hardware/OS support and expected end-of-life
288 L<https://h20195.www2.hpe.com/V2/getpdf.aspx/4AA4-7673ENW.pdf>
290 =head2 Building Dynamic Extensions on HP-UX
292 HP-UX supports dynamically loadable libraries (shared libraries).
293 Shared libraries end with the suffix .sl. On Itanium systems,
294 they end with the suffix .so.
296 Shared libraries created on a platform using a particular PA-RISC
297 version are not usable on platforms using an earlier PA-RISC version by
298 default. However, this backwards compatibility may be enabled using the
299 same +DAportable compiler flag (with the same PA-RISC 1.0 caveat
302 Shared libraries created on an Itanium platform cannot be loaded on
303 a PA-RISC platform. Shared libraries created on a PA-RISC platform
304 can only be loaded on an Itanium platform if it is a PA-RISC executable
305 that is attempting to load the PA-RISC library. A PA-RISC shared
306 library cannot be loaded into an Itanium executable nor vice-versa.
308 To create a shared library, the following steps must be performed:
310 1. Compile source modules with +z or +Z flag to create a .o module
311 which contains Position-Independent Code (PIC). The linker will
312 tell you in the next step if +Z was needed.
313 (For gcc, the appropriate flag is -fpic or -fPIC.)
315 2. Link the shared library using the -b flag. If the code calls
316 any functions in other system libraries (e.g., libm), it must
317 be included on this line.
319 (Note that these steps are usually handled automatically by the extension's
322 If these dependent libraries are not listed at shared library creation
323 time, you will get fatal "Unresolved symbol" errors at run time when the
326 You may create a shared library that refers to another library, which
327 may be either an archive library or a shared library. If this second
328 library is a shared library, this is called a "dependent library". The
329 dependent library's name is recorded in the main shared library, but it
330 is not linked into the shared library. Instead, it is loaded when the
331 main shared library is loaded. This can cause problems if you build an
332 extension on one system and move it to another system where the
333 libraries may not be located in the same place as on the first system.
335 If the referred library is an archive library, then it is treated as a
336 simple collection of .o modules (all of which must contain PIC). These
337 modules are then linked into the shared library.
339 Note that it is okay to create a library which contains a dependent
340 library that is already linked into perl.
342 Some extensions, like DB_File and Compress::Zlib use/require prebuilt
343 libraries for the perl extensions/modules to work. If these libraries
344 are built using the default configuration, it might happen that you
345 run into an error like "invalid loader fixup" during load phase.
346 HP is aware of this problem. Search the HP-UX cxx-dev forums for
347 discussions about the subject. The short answer is that B<everything>
348 (all libraries, everything) must be compiled with C<+z> or C<+Z> to be
349 PIC (position independent code). (For gcc, that would be
350 C<-fpic> or C<-fPIC>). In HP-UX 11.00 or newer the linker
351 error message should tell the name of the offending object file.
353 A more general approach is to intervene manually, as with an example for
354 the DB_File module, which requires SleepyCat's libdb.sl:
356 # cd .../db-3.2.9/build_unix
358 ... add +Z to all cflags to create shared objects
359 CFLAGS= -c $(CPPFLAGS) +Z -Ae +O2 +Onolimit \
360 -I/usr/local/include -I/usr/include/X11R6
361 CXXFLAGS= -c $(CPPFLAGS) +Z -Ae +O2 +Onolimit \
362 -I/usr/local/include -I/usr/include/X11R6
369 # ld -b -o libdb-3.2.sl *.o
370 # mv libdb-3.2.sl /usr/local/lib
374 # ln -s libdb-3.2.sl libdb.sl
376 # cd .../DB_File-1.76
383 As of db-4.2.x it is no longer needed to do this by hand. Sleepycat
384 has changed the configuration process to add +z on HP-UX automatically.
386 # cd .../db-4.2.25/build_unix
387 # env CFLAGS=+DD64 LDFLAGS=+DD64 ../dist/configure
389 should work to generate 64bit shared libraries for HP-UX 11.00 and 11i.
391 It is no longer possible to link PA-RISC 1.0 shared libraries (even
392 though the command-line flags are still present).
394 PA-RISC and Itanium object files are not interchangeable. Although
395 you may be able to use ar to create an archive library of PA-RISC
396 object files on an Itanium system, you cannot link against it using
397 an Itanium link editor.
399 =head2 The HP ANSI C Compiler
401 When using this compiler to build Perl, you should make sure that the
402 flag -Aa is added to the cpprun and cppstdin variables in the config.sh
403 file (though see the section on 64-bit perl below). If you are using a
404 recent version of the Perl distribution, these flags are set automatically.
406 Even though HP-UX 10.20 and 11.00 are not actively maintained by HP
407 anymore, updates for the HP ANSI C compiler are still available from
408 time to time, and it might be advisable to see if updates are applicable.
409 At the moment of writing, the latests available patches for 11.00 that
410 should be applied are PHSS_35098, PHSS_35175, PHSS_35100, PHSS_33036,
411 and PHSS_33902). If you have a SUM account, you can use it to search
412 for updates/patches. Enter "ANSI" as keyword.
414 =head2 The GNU C Compiler
416 When you are going to use the GNU C compiler (gcc), and you don't have
417 gcc yet, you can either build it yourself (if you feel masochistic enough)
418 from the sources (available from e.g. L<http://gcc.gnu.org/mirrors.html>)
419 or fetch a prebuilt binary from the HP porting center at
420 L<http://hpux.connect.org.uk/hppd/cgi-bin/search?term=gcc&Search=Search>
421 or from the DSPP (you need to be a member) at
422 L<http://h21007.www2.hp.com/portal/site/dspp/menuitem.863c3e4cbcdc3f3515b49c108973a801?ciid=2a08725cc2f02110725cc2f02110275d6e10RCRD&jumpid=reg_r1002_usen_c-001_title_r0001>
423 (Browse through the list, because there are often multiple versions of
424 the same package available).
426 Most mentioned distributions are depots. H.Merijn Brand has made prebuilt
427 gcc binaries available on L<http://mirrors.develooper.com/hpux/> and/or
428 L<http://www.cmve.net/~merijn/> for HP-UX 10.20 (only 32bit), HP-UX 11.00,
429 HP-UX 11.11 (HP-UX 11i v1), and HP-UX 11.23 (HP-UX 11i v2 PA-RISC) in both
430 32- and 64-bit versions. For HP-UX 11.23 IPF and HP-UX 11.31 IPF depots are
431 available too. The IPF versions do not need two versions of GNU gcc.
433 On PA-RISC you need a different compiler for 32-bit applications and for
434 64-bit applications. On PA-RISC, 32-bit objects and 64-bit objects do
435 not mix. Period. There is no different behaviour for HP C-ANSI-C or GNU
436 gcc. So if you require your perl binary to use 64-bit libraries, like
437 Oracle-64bit, you MUST build a 64-bit perl.
439 Building a 64-bit capable gcc on PA-RISC from source is possible only when
440 you have the HP C-ANSI C compiler or an already working 64-bit binary of
441 gcc available. Best performance for perl is achieved with HP's native
444 =head2 Using Large Files with Perl on HP-UX
446 Beginning with HP-UX version 10.20, files larger than 2GB (2^31 bytes)
447 may be created and manipulated. Three separate methods of doing this
448 are available. Of these methods, the best method for Perl is to compile
449 using the -Duselargefiles flag to Configure. This causes Perl to be
450 compiled using structures and functions in which these are 64 bits wide,
451 rather than 32 bits wide. (Note that this will only work with HP's ANSI
452 C compiler. If you want to compile Perl using gcc, you will have to get
453 a version of the compiler that supports 64-bit operations. See above for
456 There are some drawbacks to this approach. One is that any extension
457 which calls any file-manipulating C function will need to be recompiled
458 (just follow the usual "perl Makefile.PL; make; make test; make install"
461 The list of functions that will need to recompiled is:
462 creat, fgetpos, fopen,
463 freopen, fsetpos, fstat,
464 fstatvfs, fstatvfsdev, ftruncate,
467 open, prealloc, stat,
468 statvfs, statvfsdev, tmpfile,
469 truncate, getrlimit, setrlimit
471 Another drawback is only valid for Perl versions before 5.6.0. This
472 drawback is that the seek and tell functions (both the builtin version
473 and POSIX module version) will not perform correctly.
475 It is strongly recommended that you use this flag when you run
476 Configure. If you do not do this, but later answer the question about
477 large files when Configure asks you, you may get a configuration that
478 cannot be compiled, or that does not function as expected.
480 =head2 Threaded Perl on HP-UX
482 It is possible to compile a version of threaded Perl on any version of
483 HP-UX before 10.30, but it is strongly suggested that you be running on
484 HP-UX 11.00 at least.
486 To compile Perl with threads, add -Dusethreads to the arguments of
487 Configure. Verify that the -D_POSIX_C_SOURCE=199506L compiler flag is
488 automatically added to the list of flags. Also make sure that -lpthread
489 is listed before -lc in the list of libraries to link Perl with. The
490 hints provided for HP-UX during Configure will try very hard to get
493 HP-UX versions before 10.30 require a separate installation of a POSIX
494 threads library package. Two examples are the HP DCE package, available
495 on "HP-UX Hardware Extensions 3.0, Install and Core OS, Release 10.20,
496 April 1999 (B3920-13941)" or the Freely available PTH package, available
497 on H.Merijn's site (L<http://mirrors.develooper.com/hpux/>). The use of PTH
498 will be unsupported in perl-5.12 and up and is rather buggy in 5.11.x.
500 If you are going to use the HP DCE package, the library used for threading
501 is /usr/lib/libcma.sl, but there have been multiple updates of that
502 library over time. Perl will build with the first version, but it
503 will not pass the test suite. Older Oracle versions might be a compelling
504 reason not to update that library, otherwise please find a newer version
505 in one of the following patches: PHSS_19739, PHSS_20608, or PHSS_23672
509 d3:/usr/lib 106 > what libcma-*.1
511 HP DCE/9000 1.5 Module: libcma.sl (Export)
512 Date: Apr 29 1996 22:11:24
514 HP DCE/9000 1.5 PHSS_19739-40 Module: libcma.sl (Export)
515 Date: Sep 4 1999 01:59:07
517 HP DCE/9000 1.5 PHSS_20608 Module: libcma.1 (Export)
518 Date: Dec 8 1999 18:41:23
520 HP DCE/9000 1.5 PHSS_23672 Module: libcma.1 (Export)
521 Date: Apr 9 2001 10:01:06
524 If you choose for the PTH package, use swinstall to install pth in
525 the default location (/opt/pth), and then make symbolic links to the
526 libraries from /usr/lib
529 # ln -s /opt/pth/lib/libpth* .
531 For building perl to support Oracle, it needs to be linked with libcl
532 and libpthread. So even if your perl is an unthreaded build, these
533 libraries might be required. See "Oracle on HP-UX" below.
535 =head2 64-bit Perl on HP-UX
537 Beginning with HP-UX 11.00, programs compiled under HP-UX can take
538 advantage of the LP64 programming environment (LP64 means Longs and
539 Pointers are 64 bits wide), in which scalar variables will be able
540 to hold numbers larger than 2^32 with complete precision. Perl has
541 proven to be consistent and reliable in 64bit mode since 5.8.1 on
544 As of the date of this document, Perl is fully 64-bit compliant on
545 HP-UX 11.00 and up for both cc- and gcc builds. If you are about to
546 build a 64-bit perl with GNU gcc, please read the gcc section carefully.
548 Should a user have the need for compiling Perl in the LP64 environment,
549 use the -Duse64bitall flag to Configure. This will force Perl to be
550 compiled in a pure LP64 environment (with the +DD64 flag for HP C-ANSI-C,
551 with no additional options for GNU gcc 64-bit on PA-RISC, and with
552 -mlp64 for GNU gcc on Itanium).
553 If you want to compile Perl using gcc, you will have to get a version of
554 the compiler that supports 64-bit operations.)
556 You can also use the -Duse64bitint flag to Configure. Although there
557 are some minor differences between compiling Perl with this flag versus
558 the -Duse64bitall flag, they should not be noticeable from a Perl user's
559 perspective. When configuring -Duse64bitint using a 64bit gcc on a
560 pa-risc architecture, -Duse64bitint is silently promoted to -Duse64bitall.
562 In both cases, it is strongly recommended that you use these flags when
563 you run Configure. If you do not use do this, but later answer the
564 questions about 64-bit numbers when Configure asks you, you may get a
565 configuration that cannot be compiled, or that does not function as
568 =head2 Oracle on HP-UX
570 Using perl to connect to Oracle databases through DBI and DBD::Oracle
571 has caused a lot of people many headaches. Read README.hpux in the
572 DBD::Oracle for much more information. The reason to mention it here
573 is that Oracle requires a perl built with libcl and libpthread, the
574 latter even when perl is build without threads. Building perl using
575 all defaults, but still enabling to build DBD::Oracle later on can be
578 Configure -A prepend:libswanted='cl pthread ' ...
580 Do not forget the space before the trailing quote.
582 Also note that this does not (yet) work with all configurations,
583 it is known to fail with 64-bit versions of GCC.
585 =head2 GDBM and Threads on HP-UX
587 If you attempt to compile Perl with (POSIX) threads on an 11.X system
588 and also link in the GDBM library, then Perl will immediately core dump
589 when it starts up. The only workaround at this point is to relink the
590 GDBM library under 11.X, then relink it into Perl.
592 the error might show something like:
594 Pthread internal error: message: __libc_reinit() failed, file: ../pthreads/pthread.c, line: 1096
595 Return Pointer is 0xc082bf33
596 sh: 5345 Quit(coredump)
598 and Configure will give up.
600 =head2 NFS filesystems and utime(2) on HP-UX
602 If you are compiling Perl on a remotely-mounted NFS filesystem, the test
603 io/fs.t may fail on test #18. This appears to be a bug in HP-UX and no
604 fix is currently available.
606 =head2 HP-UX Kernel Parameters (maxdsiz) for Compiling Perl
608 By default, HP-UX comes configured with a maximum data segment size of
609 64MB. This is too small to correctly compile Perl with the maximum
610 optimization levels. You can increase the size of the maxdsiz kernel
611 parameter through the use of SAM.
613 When using the GUI version of SAM, click on the Kernel Configuration
614 icon, then the Configurable Parameters icon. Scroll down and select
615 the maxdsiz line. From the Actions menu, select the Modify Configurable
616 Parameter item. Insert the new formula into the Formula/Value box.
617 Then follow the instructions to rebuild your kernel and reboot your
620 In general, a value of 256MB (or "256*1024*1024") is sufficient for
621 Perl to compile at maximum optimization.
623 =head1 nss_delete core dump from op/pwent or op/grent
625 You may get a bus error core dump from the op/pwent or op/grent
626 tests. If compiled with -g you will see a stack trace much like
629 #0 0xc004216c in () from /usr/lib/libc.2
630 #1 0xc00d7550 in __nss_src_state_destr () from /usr/lib/libc.2
631 #2 0xc00d7768 in __nss_src_state_destr () from /usr/lib/libc.2
632 #3 0xc00d78a8 in nss_delete () from /usr/lib/libc.2
633 #4 0xc01126d8 in endpwent () from /usr/lib/libc.2
634 #5 0xd1950 in Perl_pp_epwent () from ./perl
635 #6 0x94d3c in Perl_runops_standard () from ./perl
636 #7 0x23728 in S_run_body () from ./perl
637 #8 0x23428 in perl_run () from ./perl
638 #9 0x2005c in main () from ./perl
640 The key here is the C<nss_delete> call. One workaround for this
641 bug seems to be to create add to the file F</etc/nsswitch.conf>
642 (at least) the following lines
647 Whether you are using NIS does not matter. Amazingly enough,
648 the same bug also affects Solaris.
650 =head1 error: pasting ")" and "l" does not give a valid preprocessing token
652 There seems to be a broken system header file in HP-UX 11.00 that
653 breaks perl building in 32bit mode with GNU gcc-4.x causing this
654 error. The same file for HP-UX 11.11 (even though the file is older)
655 does not show this failure, and has the correct definition, so the
656 best fix is to patch the header to match:
658 --- /usr/include/inttypes.h 2001-04-20 18:42:14 +0200
659 +++ /usr/include/inttypes.h 2000-11-14 09:00:00 +0200
661 #define UINT32_C(__c) __CONCAT_U__(__c)
663 #define INT32_C(__c) __CONCAT__(__c,l)
664 -#define UINT32_C(__c) __CONCAT__(__CONCAT_U__(__c),l)
665 +#define UINT32_C(__c) __CONCAT__(__c,ul)
668 #define INT64_C(__c) __CONCAT_L__(__c,l)
670 =head1 Redeclaration of "sendpath" with a different storage class specifier
672 The following compilation warnings may happen in HP-UX releases
673 earlier than 11.31 but are harmless:
675 cc: "/usr/include/sys/socket.h", line 535: warning 562:
676 Redeclaration of "sendfile" with a different storage class
677 specifier: "sendfile" will have internal linkage.
678 cc: "/usr/include/sys/socket.h", line 536: warning 562:
679 Redeclaration of "sendpath" with a different storage class
680 specifier: "sendpath" will have internal linkage.
682 They seem to be caused by broken system header files, and also other
683 open source projects are seeing them. The following HP-UX patches
684 should make the warnings go away:
686 CR JAGae12001: PHNE_27063
687 Warning 562 on sys/socket.h due to redeclaration of prototypes
690 Warning 562 from socket.h sendpath/sendfile -D_FILEFFSET_BITS=64
692 CR JAGae73470 (11.23)
693 ER: Compiling socket.h with cc -D_FILEFFSET_BITS=64 warning 267/562
697 HP-UX 11 Y2K patch "Y2K-1100 B.11.00.B0125 HP-UX Core OS Year 2000
698 Patch Bundle" has been reported to break the io/fs test #18 which
699 tests whether utime() can change timestamps. The Y2K patch seems to
700 break utime() so that over NFS the timestamps do not get changed
701 (on local filesystems utime() still works). This has probably been
702 fixed on your system by now.
706 H.Merijn Brand <h.m.brand@xs4all.nl>
707 Jeff Okamoto <okamoto@corp.hp.com>
709 With much assistance regarding shared libraries from Marc Sabatella.