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