1PERLHPUX(1) Perl Programmers Reference Guide PERLHPUX(1)
2
6 perlhpux - 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.
21 That build was a portable hppa-1.1 multithread build that supports
23 large files compiled with gcc-2.9-hppa-991112.
24 If you perform a new installation, then (a newer) Perl will be
26 installed automatically. Pre-installed HP-UX systems now have more
27 recent versions of Perl and the updated modules.
28 The official (threaded) builds from HP, as they are shipped on the
30 Application DVD/CD's are available on
31 <http://www.software.hp.com/portal/swdepot/displayProductInfo.do?productNumber=PERL>
32 for both PA-RISC and IPF (Itanium Processor Family). They are built
33 with the HP ANSI-C compiler. Up till 5.8.8 that was done by
34 ActiveState.
35 To see what version is included on the DVD (assumed here to be mounted
37 on /cdrom), issue this command:
38 # swlist -s /cdrom perl
40 # perl D.5.8.8.B 5.8.8 Perl Programming Language
41 perl.Perl5-32 D.5.8.8.B 32-bit 5.8.8 Perl Programming Language
42 with Extensions
43 perl.Perl5-64 D.5.8.8.B 64-bit 5.8.8 Perl Programming Language
44 with Extensions
45 To see what is installed on your system:
47 # swlist -R perl
49 # perl E.5.8.8.J Perl Programming Language
50 # perl.Perl5-32 E.5.8.8.J 32-bit Perl Programming Language
51 with Extensions
52 perl.Perl5-32.PERL-MAN E.5.8.8.J 32-bit Perl Man Pages for IA
53 perl.Perl5-32.PERL-RUN E.5.8.8.J 32-bit Perl Binaries for IA
54 # perl.Perl5-64 E.5.8.8.J 64-bit Perl Programming Language
55 with Extensions
56 perl.Perl5-64.PERL-MAN E.5.8.8.J 64-bit Perl Man Pages for IA
57 perl.Perl5-64.PERL-RUN E.5.8.8.J 64-bit Perl Binaries for IA
58 Using perl from HP's porting centre
60 HP porting centre tries to keep up with customer demand and release
61 updates from the Open Source community. Having precompiled Perl
62 binaries available is obvious, though "up-to-date" is something
63 relative. At the moment of writing perl-5.10.1 and 5.28.0 were
64 available.
65 The HP porting centres are limited in what systems they are allowed to
67 port to and they usually choose the two most recent OS versions
68 available.
69 HP has asked the porting centre to move Open Source binaries from /opt
71 to /usr/local, so binaries produced since the start of July 2002 are
72 located in /usr/local.
73 One of HP porting centres URL's is <http://hpux.connect.org.uk/> The
75 port currently available is built with GNU gcc. As porting modern GNU
76 gcc is extremely hard on HP-UX, they are stuck at version gcc-4.2.3.
77 Other prebuilt perl binaries
79 To get more perl depots for the whole range of HP-UX, visit H.Merijn
80 Brand's site at <http://mirrors.develooper.com/hpux/#Perl>. Carefully
81 read the notes to see if the available versions suit your needs.
82 Compiling Perl 5 on HP-UX
84 When compiling Perl, you must use an ANSI C compiler. The C compiler
85 that ships with all HP-UX systems is a K&R compiler that should only be
86 used to build new kernels.
87 Perl can be compiled with either HP's ANSI C compiler or with gcc. The
89 former is recommended, as not only can it compile Perl with no
90 difficulty, but also can take advantage of features listed later that
91 require the use of HP compiler-specific command-line flags.
92 If you decide to use gcc, make sure your installation is recent and
94 complete, and be sure to read the Perl INSTALL file for more gcc-
95 specific details.
96 PA-RISC
98 The last and final version of PA-RISC is 2.0, HP no longer sells any
99 system with these CPU's.
100 HP's HP9000 Unix systems run on HP's own Precision Architecture (PA-
102 RISC) chip. HP-UX used to run on the Motorola MC68000 family of chips,
103 but any machine with this chip in it is quite obsolete and this
104 document will not attempt to address issues for compiling Perl on the
105 Motorola chipset. Even though PA-RISC hardware is not sold anymore, a
106 lot of machines still running on these CPU's can be found in the wild.
107 The last order date for HP 9000 systems was December 31, 2008.
109 HP PA-RISC systems are usually referred to with model description "HP
111 9000". The last CPU in this series is the PA-8900. Support for PA-
112 RISC architectured machines officially ended as shown in the following
113 table:
114 PA-RISC End-of-Life Roadmap
116 +--------+----------------+----------------+-----------------+
117 | HP9000 | Superdome | PA-8700 | Spring 2011 |
118 | 4-128 | | PA-8800/sx1000 | Summer 2012 |
119 | cores | | PA-8900/sx1000 | 2014 |
120 | | | PA-8900/sx2000 | 2015 |
121 +--------+----------------+----------------+-----------------+
122 | HP9000 | rp7410, rp8400 | PA-8700 | Spring 2011 |
123 | 2-32 | rp7420, rp8420 | PA-8800/sx1000 | 2012 |
124 | cores | rp7440, rp8440 | PA-8900/sx1000 | Autumn 2013 |
125 | | | PA-8900/sx2000 | 2015 |
126 +--------+----------------+----------------+-----------------+
127 | HP9000 | rp44x0 | PA-8700 | Spring 2011 |
128 | 1-8 | | PA-8800/rp44x0 | 2012 |
129 | cores | | PA-8900/rp44x0 | 2014 |
130 +--------+----------------+----------------+-----------------+
131 | HP9000 | rp34x0 | PA-8700 | Spring 2011 |
132 | 1-4 | | PA-8800/rp34x0 | 2012 |
133 | cores | | PA-8900/rp34x0 | 2014 |
134 +--------+----------------+----------------+-----------------+
135 A complete list of models at the time the OS was built is in the file
137 /usr/sam/lib/mo/sched.models. The first column corresponds to the last
138 part of the output of the "model" command. The second column is the
139 PA-RISC version and the third column is the exact chip type used.
140 (Start browsing at the bottom to prevent confusion ;-)
141 # model
143 9000/800/L1000-44
144 # grep L1000-44 /usr/sam/lib/mo/sched.models
145 L1000-44 2.0 PA8500
146 PA-RISC 1.0
148 The original version of PA-RISC, HP no longer sells any system with
149 this chip.
150 The following systems contained PA-RISC 1.0 chips:
152 600, 635, 645, 808, 815, 822, 825, 832, 834, 835, 840, 842, 845, 850,
154 852, 855, 860, 865, 870, 890
155 PA-RISC 1.1
157 An upgrade to the PA-RISC design, it shipped for many years in many
158 different system.
159 The following systems contain with PA-RISC 1.1 chips:
161 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 PA-RISC 2.0
174 The most recent upgrade to the PA-RISC design, it added support for
175 64-bit integer data.
176 As of the date of this document's last update, the following systems
178 contain PA-RISC 2.0 chips:
179 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 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 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 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 The current naming convention is:
201 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 Portability Between PA-RISC Versions
220 An executable compiled on a PA-RISC 2.0 platform will not execute on a
221 PA-RISC 1.1 platform, even if they are running the same version of HP-
222 UX. If you are building Perl on a PA-RISC 2.0 platform and want that
223 Perl to also run on a PA-RISC 1.1, the compiler flags +DAportable and
224 +DS32 should be used.
225 It is no longer possible to compile PA-RISC 1.0 executables on either
227 the PA-RISC 1.1 or 2.0 platforms. The command-line flags are accepted,
228 but the resulting executable will not run when transferred to a PA-RISC
229 1.0 system.
230 Itanium Processor Family (IPF) and HP-UX
232 HP-UX also runs on the newer Itanium processor. This requires the use
233 of HP-UX version 11.23 (11i v2) or 11.31 (11i v3), and with the
234 exception of a few differences detailed below and in later sections,
235 Perl should compile with no problems.
236 Although PA-RISC binaries can run on Itanium systems, you should not
238 attempt to use a PA-RISC version of Perl on an Itanium system. This is
239 because shared libraries created on an Itanium system cannot be loaded
240 while running a PA-RISC executable.
241 HP Itanium 2 systems are usually referred to with model description "HP
243 Integrity".
244 Itanium, Itanium 2 & Madison 6
246 HP also ships servers with the 128-bit Itanium processor(s). The cx26x0
247 is told to have Madison 6. As of the date of this document's last
248 update, the following systems contain Itanium or Itanium 2 chips (this
249 is likely to be out of date):
250 BL60p, BL860c, BL870c, BL890c, cx2600, cx2620, rx1600, rx1620, rx2600,
252 rx2600hptc, rx2620, rx2660, rx2800, rx3600, rx4610, rx4640, rx5670,
253 rx6600, rx7420, rx7620, rx7640, rx8420, rx8620, rx8640, rx9610,
254 sx1000, sx2000
255 To see all about your machine, type
257 # model
259 ia64 hp server rx2600
260 # /usr/contrib/bin/machinfo
261 HP-UX versions
263 Not all architectures (PA = PA-RISC, IPF = Itanium Processor Family)
264 support all versions of HP-UX, here is a short list
265 HP-UX version Kernel Architecture End-of-factory support
267 ------------- ------ ------------ ----------------------------------
268 10.20 32 bit PA 30-Jun-2003
269 11.00 32/64 PA 31-Dec-2006
270 11.11 11i v1 32/64 PA 31-Dec-2015
271 11.22 11i v2 64 IPF 30-Apr-2004
272 11.23 11i v2 64 PA & IPF 31-Dec-2015
273 11.31 11i v3 64 PA & IPF 31-Dec-2020 (PA) 31-Dec-2025 (IPF)
274 See for the full list of hardware/OS support and expected end-of-life
276 <https://h20195.www2.hpe.com/V2/getpdf.aspx/4AA4-7673ENW.pdf>
277 Building Dynamic Extensions on HP-UX
279 HP-UX supports dynamically loadable libraries (shared libraries).
280 Shared libraries end with the suffix .sl. On Itanium systems, they end
281 with the suffix .so.
282 Shared libraries created on a platform using a particular PA-RISC
284 version are not usable on platforms using an earlier PA-RISC version by
285 default. However, this backwards compatibility may be enabled using
286 the same +DAportable compiler flag (with the same PA-RISC 1.0 caveat
287 mentioned above).
288 Shared libraries created on an Itanium platform cannot be loaded on a
290 PA-RISC platform. Shared libraries created on a PA-RISC platform can
291 only be loaded on an Itanium platform if it is a PA-RISC executable
292 that is attempting to load the PA-RISC library. A PA-RISC shared
293 library cannot be loaded into an Itanium executable nor vice-versa.
294 To create a shared library, the following steps must be performed:
296 1. Compile source modules with +z or +Z flag to create a .o module
298 which contains Position-Independent Code (PIC). The linker will
299 tell you in the next step if +Z was needed.
300 (For gcc, the appropriate flag is -fpic or -fPIC.)
301 2. Link the shared library using the -b flag. If the code calls
303 any functions in other system libraries (e.g., libm), it must
304 be included on this line.
305 (Note that these steps are usually handled automatically by the
307 extension's Makefile).
308 If these dependent libraries are not listed at shared library creation
310 time, you will get fatal "Unresolved symbol" errors at run time when
311 the library is loaded.
312 You may create a shared library that refers to another library, which
314 may be either an archive library or a shared library. If this second
315 library is a shared library, this is called a "dependent library". The
316 dependent library's name is recorded in the main shared library, but it
317 is not linked into the shared library. Instead, it is loaded when the
318 main shared library is loaded. This can cause problems if you build an
319 extension on one system and move it to another system where the
320 libraries may not be located in the same place as on the first system.
321 If the referred library is an archive library, then it is treated as a
323 simple collection of .o modules (all of which must contain PIC). These
324 modules are then linked into the shared library.
325 Note that it is okay to create a library which contains a dependent
327 library that is already linked into perl.
328 Some extensions, like DB_File and Compress::Zlib use/require prebuilt
330 libraries for the perl extensions/modules to work. If these libraries
331 are built using the default configuration, it might happen that you run
332 into an error like "invalid loader fixup" during load phase. HP is
333 aware of this problem. Search the HP-UX cxx-dev forums for discussions
334 about the subject. The short answer is that everything (all libraries,
335 everything) must be compiled with "+z" or "+Z" to be PIC (position
336 independent code). (For gcc, that would be "-fpic" or "-fPIC"). In
337 HP-UX 11.00 or newer the linker error message should tell the name of
338 the offending object file.
339 A more general approach is to intervene manually, as with an example
341 for the DB_File module, which requires SleepyCat's libdb.sl:
342 # cd .../db-3.2.9/build_unix
344 # vi Makefile
345 ... add +Z to all cflags to create shared objects
346 CFLAGS= -c $(CPPFLAGS) +Z -Ae +O2 +Onolimit \
347 -I/usr/local/include -I/usr/include/X11R6
348 CXXFLAGS= -c $(CPPFLAGS) +Z -Ae +O2 +Onolimit \
349 -I/usr/local/include -I/usr/include/X11R6
350 # make clean
352 # make
353 # mkdir tmp
354 # cd tmp
355 # ar x ../libdb.a
356 # ld -b -o libdb-3.2.sl *.o
357 # mv libdb-3.2.sl /usr/local/lib
358 # rm *.o
359 # cd /usr/local/lib
360 # rm -f libdb.sl
361 # ln -s libdb-3.2.sl libdb.sl
362 # cd .../DB_File-1.76
364 # make distclean
365 # perl Makefile.PL
366 # make
367 # make test
368 # make install
369 As of db-4.2.x it is no longer needed to do this by hand. Sleepycat has
371 changed the configuration process to add +z on HP-UX automatically.
372 # cd .../db-4.2.25/build_unix
374 # env CFLAGS=+DD64 LDFLAGS=+DD64 ../dist/configure
375 should work to generate 64bit shared libraries for HP-UX 11.00 and 11i.
377 It is no longer possible to link PA-RISC 1.0 shared libraries (even
379 though the command-line flags are still present).
380 PA-RISC and Itanium object files are not interchangeable. Although you
382 may be able to use ar to create an archive library of PA-RISC object
383 files on an Itanium system, you cannot link against it using an Itanium
384 link editor.
385 The HP ANSI C Compiler
387 When using this compiler to build Perl, you should make sure that the
388 flag -Aa is added to the cpprun and cppstdin variables in the config.sh
389 file (though see the section on 64-bit perl below). If you are using a
390 recent version of the Perl distribution, these flags are set
391 automatically.
392 Even though HP-UX 10.20 and 11.00 are not actively maintained by HP
394 anymore, updates for the HP ANSI C compiler are still available from
395 time to time, and it might be advisable to see if updates are
396 applicable. At the moment of writing, the latests available patches
397 for 11.00 that should be applied are PHSS_35098, PHSS_35175,
398 PHSS_35100, PHSS_33036, and PHSS_33902). If you have a SUM account, you
399 can use it to search for updates/patches. Enter "ANSI" as keyword.
400 The GNU C Compiler
402 When you are going to use the GNU C compiler (gcc), and you don't have
403 gcc yet, you can either build it yourself (if you feel masochistic
404 enough) from the sources (available from e.g.
405 <http://gcc.gnu.org/mirrors.html>) or fetch a prebuilt binary from the
406 HP porting center at
407 <http://hpux.connect.org.uk/hppd/cgi-bin/search?term=gcc&Search=Search>
408 or from the DSPP (you need to be a member) at
409 <http://h21007.www2.hp.com/portal/site/dspp/menuitem.863c3e4cbcdc3f3515b49c108973a801?ciid=2a08725cc2f02110725cc2f02110275d6e10RCRD&jumpid=reg_r1002_usen_c-001_title_r0001>
410 (Browse through the list, because there are often multiple versions of
411 the same package available).
412 Most mentioned distributions are depots. H.Merijn Brand has made
414 prebuilt gcc binaries available on
415 <http://mirrors.develooper.com/hpux/> and/or
416 <http://www.cmve.net/~merijn/> for HP-UX 10.20 (only 32bit), HP-UX
417 11.00, HP-UX 11.11 (HP-UX 11i v1), and HP-UX 11.23 (HP-UX 11i v2 PA-
418 RISC) in both 32- and 64-bit versions. For HP-UX 11.23 IPF and HP-UX
419 11.31 IPF depots are available too. The IPF versions do not need two
420 versions of GNU gcc.
421 On PA-RISC you need a different compiler for 32-bit applications and
423 for 64-bit applications. On PA-RISC, 32-bit objects and 64-bit objects
424 do not mix. Period. There is no different behaviour for HP C-ANSI-C or
425 GNU gcc. So if you require your perl binary to use 64-bit libraries,
426 like Oracle-64bit, you MUST build a 64-bit perl.
427 Building a 64-bit capable gcc on PA-RISC from source is possible only
429 when you have the HP C-ANSI C compiler or an already working 64-bit
430 binary of gcc available. Best performance for perl is achieved with
431 HP's native compiler.
432 Using Large Files with Perl on HP-UX
434 Beginning with HP-UX version 10.20, files larger than 2GB (2^31 bytes)
435 may be created and manipulated. Three separate methods of doing this
436 are available. Of these methods, the best method for Perl is to
437 compile using the -Duselargefiles flag to Configure. This causes Perl
438 to be compiled using structures and functions in which these are 64
439 bits wide, rather than 32 bits wide. (Note that this will only work
440 with HP's ANSI C compiler. If you want to compile Perl using gcc, you
441 will have to get a version of the compiler that supports 64-bit
442 operations. See above for where to find it.)
443 There are some drawbacks to this approach. One is that any extension
445 which calls any file-manipulating C function will need to be recompiled
446 (just follow the usual "perl Makefile.PL; make; make test; make
447 install" procedure).
448 The list of functions that will need to recompiled is:
450 creat, fgetpos, fopen,
451 freopen, fsetpos, fstat,
452 fstatvfs, fstatvfsdev, ftruncate,
453 ftw, lockf, lseek,
454 lstat, mmap, nftw,
455 open, prealloc, stat,
456 statvfs, statvfsdev, tmpfile,
457 truncate, getrlimit, setrlimit
458 Another drawback is only valid for Perl versions before 5.6.0. This
460 drawback is that the seek and tell functions (both the builtin version
461 and POSIX module version) will not perform correctly.
462 It is strongly recommended that you use this flag when you run
464 Configure. If you do not do this, but later answer the question about
465 large files when Configure asks you, you may get a configuration that
466 cannot be compiled, or that does not function as expected.
467 Threaded Perl on HP-UX
469 It is possible to compile a version of threaded Perl on any version of
470 HP-UX before 10.30, but it is strongly suggested that you be running on
471 HP-UX 11.00 at least.
472 To compile Perl with threads, add -Dusethreads to the arguments of
474 Configure. Verify that the -D_POSIX_C_SOURCE=199506L compiler flag is
475 automatically added to the list of flags. Also make sure that
476 -lpthread is listed before -lc in the list of libraries to link Perl
477 with. The hints provided for HP-UX during Configure will try very hard
478 to get this right for you.
479 HP-UX versions before 10.30 require a separate installation of a POSIX
481 threads library package. Two examples are the HP DCE package, available
482 on "HP-UX Hardware Extensions 3.0, Install and Core OS, Release 10.20,
483 April 1999 (B3920-13941)" or the Freely available PTH package,
484 available on H.Merijn's site (<http://mirrors.develooper.com/hpux/>).
485 The use of PTH will be unsupported in perl-5.12 and up and is rather
486 buggy in 5.11.x.
487 If you are going to use the HP DCE package, the library used for
489 threading is /usr/lib/libcma.sl, but there have been multiple updates
490 of that library over time. Perl will build with the first version, but
491 it will not pass the test suite. Older Oracle versions might be a
492 compelling reason not to update that library, otherwise please find a
493 newer version in one of the following patches: PHSS_19739, PHSS_20608,
494 or PHSS_23672
495 reformatted output:
497 d3:/usr/lib 106 > what libcma-*.1
499 libcma-00000.1:
500 HP DCE/9000 1.5 Module: libcma.sl (Export)
501 Date: Apr 29 1996 22:11:24
502 libcma-19739.1:
503 HP DCE/9000 1.5 PHSS_19739-40 Module: libcma.sl (Export)
504 Date: Sep 4 1999 01:59:07
505 libcma-20608.1:
506 HP DCE/9000 1.5 PHSS_20608 Module: libcma.1 (Export)
507 Date: Dec 8 1999 18:41:23
508 libcma-23672.1:
509 HP DCE/9000 1.5 PHSS_23672 Module: libcma.1 (Export)
510 Date: Apr 9 2001 10:01:06
511 d3:/usr/lib 107 >
512 If you choose for the PTH package, use swinstall to install pth in the
514 default location (/opt/pth), and then make symbolic links to the
515 libraries from /usr/lib
516 # cd /usr/lib
518 # ln -s /opt/pth/lib/libpth* .
519 For building perl to support Oracle, it needs to be linked with libcl
521 and libpthread. So even if your perl is an unthreaded build, these
522 libraries might be required. See "Oracle on HP-UX" below.
523 64-bit Perl on HP-UX
525 Beginning with HP-UX 11.00, programs compiled under HP-UX can take
526 advantage of the LP64 programming environment (LP64 means Longs and
527 Pointers are 64 bits wide), in which scalar variables will be able to
528 hold numbers larger than 2^32 with complete precision. Perl has proven
529 to be consistent and reliable in 64bit mode since 5.8.1 on all HP-UX
530 11.xx.
531 As of the date of this document, Perl is fully 64-bit compliant on HP-
533 UX 11.00 and up for both cc- and gcc builds. If you are about to build
534 a 64-bit perl with GNU gcc, please read the gcc section carefully.
535 Should a user have the need for compiling Perl in the LP64 environment,
537 use the -Duse64bitall flag to Configure. This will force Perl to be
538 compiled in a pure LP64 environment (with the +DD64 flag for HP C-ANSI-
539 C, with no additional options for GNU gcc 64-bit on PA-RISC, and with
540 -mlp64 for GNU gcc on Itanium). If you want to compile Perl using gcc,
541 you will have to get a version of the compiler that supports 64-bit
542 operations.)
543 You can also use the -Duse64bitint flag to Configure. Although there
545 are some minor differences between compiling Perl with this flag versus
546 the -Duse64bitall flag, they should not be noticeable from a Perl
547 user's perspective. When configuring -Duse64bitint using a 64bit gcc on
548 a pa-risc architecture, -Duse64bitint is silently promoted to
549 -Duse64bitall.
550 In both cases, it is strongly recommended that you use these flags when
552 you run Configure. If you do not use do this, but later answer the
553 questions about 64-bit numbers when Configure asks you, you may get a
554 configuration that cannot be compiled, or that does not function as
555 expected.
556 Oracle on HP-UX
558 Using perl to connect to Oracle databases through DBI and DBD::Oracle
559 has caused a lot of people many headaches. Read README.hpux in the
560 DBD::Oracle for much more information. The reason to mention it here is
561 that Oracle requires a perl built with libcl and libpthread, the latter
562 even when perl is build without threads. Building perl using all
563 defaults, but still enabling to build DBD::Oracle later on can be
564 achieved using
565 Configure -A prepend:libswanted='cl pthread ' ...
567 Do not forget the space before the trailing quote.
569 Also note that this does not (yet) work with all configurations, it is
571 known to fail with 64-bit versions of GCC.
572 GDBM and Threads on HP-UX
574 If you attempt to compile Perl with (POSIX) threads on an 11.X system
575 and also link in the GDBM library, then Perl will immediately core dump
576 when it starts up. The only workaround at this point is to relink the
577 GDBM library under 11.X, then relink it into Perl.
578 the error might show something like:
580 Pthread internal error: message: __libc_reinit() failed, file:
582 ../pthreads/pthread.c, line: 1096 Return Pointer is 0xc082bf33 sh: 5345
583 Quit(coredump)
584 and Configure will give up.
586 NFS filesystems and utime(2) on HP-UX
588 If you are compiling Perl on a remotely-mounted NFS filesystem, the
589 test io/fs.t may fail on test #18. This appears to be a bug in HP-UX
590 and no fix is currently available.
591 HP-UX Kernel Parameters (maxdsiz) for Compiling Perl
593 By default, HP-UX comes configured with a maximum data segment size of
594 64MB. This is too small to correctly compile Perl with the maximum
595 optimization levels. You can increase the size of the maxdsiz kernel
596 parameter through the use of SAM.
597 When using the GUI version of SAM, click on the Kernel Configuration
599 icon, then the Configurable Parameters icon. Scroll down and select
600 the maxdsiz line. From the Actions menu, select the Modify
601 Configurable Parameter item. Insert the new formula into the
602 Formula/Value box. Then follow the instructions to rebuild your kernel
603 and reboot your system.
604 In general, a value of 256MB (or "256*1024*1024") is sufficient for
606 Perl to compile at maximum optimization.
607
609 You may get a bus error core dump from the op/pwent or op/grent tests.
610 If compiled with -g you will see a stack trace much like the following:
611 #0 0xc004216c in () from /usr/lib/libc.2
613 #1 0xc00d7550 in __nss_src_state_destr () from /usr/lib/libc.2
614 #2 0xc00d7768 in __nss_src_state_destr () from /usr/lib/libc.2
615 #3 0xc00d78a8 in nss_delete () from /usr/lib/libc.2
616 #4 0xc01126d8 in endpwent () from /usr/lib/libc.2
617 #5 0xd1950 in Perl_pp_epwent () from ./perl
618 #6 0x94d3c in Perl_runops_standard () from ./perl
619 #7 0x23728 in S_run_body () from ./perl
620 #8 0x23428 in perl_run () from ./perl
621 #9 0x2005c in main () from ./perl
622 The key here is the "nss_delete" call. One workaround for this bug
624 seems to be to create add to the file /etc/nsswitch.conf (at least) the
625 following lines
626 group: files
628 passwd: files
629 Whether you are using NIS does not matter. Amazingly enough, the same
631 bug also affects Solaris.
632
634 There seems to be a broken system header file in HP-UX 11.00 that
635 breaks perl building in 32bit mode with GNU gcc-4.x causing this error.
636 The same file for HP-UX 11.11 (even though the file is older) does not
637 show this failure, and has the correct definition, so the best fix is
638 to patch the header to match:
639 --- /usr/include/inttypes.h 2001-04-20 18:42:14 +0200
641 +++ /usr/include/inttypes.h 2000-11-14 09:00:00 +0200
642 @@ -72,7 +72,7 @@
643 #define UINT32_C(__c) __CONCAT_U__(__c)
644 #else /* __LP64 */
645 #define INT32_C(__c) __CONCAT__(__c,l)
646 -#define UINT32_C(__c) __CONCAT__(__CONCAT_U__(__c),l)
647 +#define UINT32_C(__c) __CONCAT__(__c,ul)
648 #endif /* __LP64 */
649 #define INT64_C(__c) __CONCAT_L__(__c,l)
651
653 The following compilation warnings may happen in HP-UX releases earlier
654 than 11.31 but are harmless:
655 cc: "/usr/include/sys/socket.h", line 535: warning 562:
657 Redeclaration of "sendfile" with a different storage class
658 specifier: "sendfile" will have internal linkage.
659 cc: "/usr/include/sys/socket.h", line 536: warning 562:
660 Redeclaration of "sendpath" with a different storage class
661 specifier: "sendpath" will have internal linkage.
662 They seem to be caused by broken system header files, and also other
664 open source projects are seeing them. The following HP-UX patches
665 should make the warnings go away:
666 CR JAGae12001: PHNE_27063
668 Warning 562 on sys/socket.h due to redeclaration of prototypes
669 CR JAGae16787:
671 Warning 562 from socket.h sendpath/sendfile -D_FILEFFSET_BITS=64
672 CR JAGae73470 (11.23)
674 ER: Compiling socket.h with cc -D_FILEFFSET_BITS=64 warning 267/562
675
677 HP-UX 11 Y2K patch "Y2K-1100 B.11.00.B0125 HP-UX Core OS Year 2000
678 Patch Bundle" has been reported to break the io/fs test #18 which tests
679 whether utime() can change timestamps. The Y2K patch seems to break
680 utime() so that over NFS the timestamps do not get changed (on local
681 filesystems utime() still works). This has probably been fixed on your
682 system by now.
683
685 H.Merijn Brand <h.m.brand@xs4all.nl> Jeff Okamoto <okamoto@corp.hp.com>
686 With much assistance regarding shared libraries from Marc Sabatella.
688perl v5.30.1 2019-11-29 PERLHPUX(1)