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