Debian Codegraph @

upstream/fedora-44/man1/perlhpux.1

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