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