Debian Codegraph @

upstream/debian-unstable/man1/perlhpux.1

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