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