This is a live mirror of the Perl 5 development currently hosted at https://github.com/perl/perl5
Re: gcc on HP
[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
17As of application release September 2001, HP-UX 11.00 is shipped with
210b36aa 18perl-5.6.1 in /opt/perl. The first occurrence is on CD 5012-7954 and
c3c48d5c
JH
19can be installed using
20
21 swinstall -s /cdrom perl
22
23assuming you have mounted that CD on /cdrom. In this version the
24following modules are installed:
25
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
34
35The build is a portable hppa-1.1 multithread build that supports large
36files compiled with gcc-2.9-hppa-991112
37
38If you perform a new installation, then Perl will be installed
39automatically.
40
f2a260d6
GS
41=head2 Compiling Perl 5 on HP-UX
42
60ed1d8c
GS
43When compiling Perl, you must use an ANSI C compiler. The C compiler
44that ships with all HP-UX systems is a K&R compiler that should only be
45used to build new kernels.
f2a260d6
GS
46
47Perl can be compiled with either HP's ANSI C compiler or with gcc. The
60ed1d8c
GS
48former is recommended, as not only can it compile Perl with no
49difficulty, but also can take advantage of features listed later that
50require the use of HP compiler-specific command-line flags.
f2a260d6 51
60ed1d8c
GS
52If you decide to use gcc, make sure your installation is recent and
53complete, and be sure to read the Perl README file for more gcc-specific
54details.
f2a260d6
GS
55
56=head2 PA-RISC
57
60ed1d8c
GS
58HP's current Unix systems run on its own Precision Architecture
59(PA-RISC) chip. HP-UX used to run on the Motorola MC68000 family of
60chips, but any machine with this chip in it is quite obsolete and this
61document will not attempt to address issues for compiling Perl on the
62Motorola chipset.
f2a260d6 63
60ed1d8c
GS
64The most recent version of PA-RISC at the time of this document's last
65update is 2.0.
f2a260d6
GS
66
67=head2 PA-RISC 1.0
68
69The original version of PA-RISC, HP no longer sells any system with this chip.
70
13e84f2c 71The following systems contained PA-RISC 1.0 chips:
f2a260d6 72
1db6f61a
MB
73 600, 635, 645, 808, 815, 822, 825, 832, 834, 835, 840, 842, 845, 850,
74 852, 855, 860, 865, 870, 890
f2a260d6
GS
75
76=head2 PA-RISC 1.1
77
78An upgrade to the PA-RISC design, it shipped for many years in many different
79system.
80
81The following systems contain with PA-RISC 1.1 chips:
82
1db6f61a
MB
83 705, 710, 712, 715, 720, 722, 725, 728, 730, 735, 742, 743, 744, 745,
84 747, 750, 755, 770, 777, 778, 779, 800, 801, 803, 806, 807, 809, 811,
85 813, 816, 817, 819, 821, 826, 827, 829, 831, 837, 839, 841, 847, 849,
86 851, 856, 857, 859, 867, 869, 877, 887, 891, 892, 897, A180, A180C,
c9b4021b
MB
87 B115, B120, B132L, B132L+, B160L, B180L, C100, C110, C115, C120,
88 C160L, D200, D210, D220, D230, D250, D260, D310, D320, D330, D350,
89 D360, D410, DX0, DX5, DXO, E25, E35, E45, E55, F10, F20, F30, G30,
90 G40, G50, G60, G70, H20, H30, H40, H50, H60, H70, I30, I40, I50, I60,
91 I70, J200, J210, J210XC, K100, K200, K210, K220, K230, K400, K410,
92 K420, S700i, S715, S744, S760, T500, T520
f2a260d6
GS
93
94=head2 PA-RISC 2.0
95
60ed1d8c
GS
96The most recent upgrade to the PA-RISC design, it added support for
9764-bit integer data.
f2a260d6 98
60ed1d8c 99As of the date of this document's last update, the following systems
d464cda8 100contain PA-RISC 2.0 chips:
f2a260d6 101
1db6f61a
MB
102 700, 780, 781, 782, 783, 785, 802, 804, 810, 820, 861, 871, 879, 889,
103 893, 895, 896, 898, 899, A400, A500, B1000, B2000, C130, C140, C160,
104 C180, C180+, C180-XP, C200+, C400+, C3000, C360, C3600, CB260, D270,
105 D280, D370, D380, D390, D650, J220, J2240, J280, J282, J400, J410,
106 J5000, J5500XM, J5600, J7000, J7600, K250, K260, K260-EG, K270, K360,
107 K370, K380, K450, K460, K460-EG, K460-XP, K470, K570, K580, L1000,
d464cda8
MB
108 L2000, L3000, N4000, R380, R390, RP2400, RP2430, RP2450, RP2470,
109 RP5400, RP5430, RP5450, RP5470, RP7400, RP7410, RP8400, SD16000,
110 SD32000, SD64000, T540, T600, V2000, V2200, V2250, V2500, V2600
1a4e8251
MB
111
112=head2 Itanium
113
114HP also ships servers with the 128-bit Itanium processor(s). As of the
115date of this document's last update, the following systems contain
116Itanium chips (this is very likely to be out of date):
117
2925712a 118 RX4610, RX9610
f2a260d6 119
d66be8f9 120A complete list of models at the time the OS was built is in the file
60ed1d8c
GS
121/opt/langtools/lib/sched.models. The first column corresponds to the
122output of the "uname -m" command (without the leading "9000/"). The
123second column is the PA-RISC version and the third column is the exact
42be3f00 124chip type used. (Start browsing at the bottom to prevent confusion ;-)
d66be8f9 125
f2a260d6
GS
126=head2 Portability Between PA-RISC Versions
127
128An executable compiled on a PA-RISC 2.0 platform will not execute on a
60ed1d8c
GS
129PA-RISC 1.1 platform, even if they are running the same version of
130HP-UX. If you are building Perl on a PA-RISC 2.0 platform and want that
d1be9408 131Perl to also run on a PA-RISC 1.1, the compiler flags +DAportable and
60ed1d8c 132+DS32 should be used.
f2a260d6 133
60ed1d8c 134It is no longer possible to compile PA-RISC 1.0 executables on either
13e84f2c
JH
135the PA-RISC 1.1 or 2.0 platforms. The command-line flags are accepted,
136but the resulting executable will not run when transferred to a PA-RISC
1371.0 system.
138
a83b6f46 139=head2 Itanium Processor Family and HP-UX
13e84f2c
JH
140
141HP-UX also runs on the new Itanium processor. This requires the use
142of a different version of HP-UX (currently 11.20), and with the exception
143of a few differences detailed below and in later sections, Perl should
144compile with no problems.
145
146Although PA-RISC binaries can run on Itanium systems, you should not
147attempt to use a PA-RISC version of Perl on an Itanium system. This is
148because shared libraries created on an Itanium system cannot be loaded
149while running a PA-RISC executable.
f2a260d6
GS
150
151=head2 Building Dynamic Extensions on HP-UX
152
153HP-UX supports dynamically loadable libraries (shared libraries).
13e84f2c
JH
154Shared libraries end with the suffix .sl. On Itanium systems,
155they end with the suffix .so.
f2a260d6 156
60ed1d8c
GS
157Shared libraries created on a platform using a particular PA-RISC
158version are not usable on platforms using an earlier PA-RISC version by
159default. However, this backwards compatibility may be enabled using the
160same +DAportable compiler flag (with the same PA-RISC 1.0 caveat
161mentioned above).
f2a260d6 162
13e84f2c
JH
163Shared libraries created on an Itanium platform cannot be loaded on
164a PA-RISC platform. Shared libraries created on a PA-RISC platform
165can only be loaded on an Itanium platform if it is a PA-RISC executable
166that is attempting to load the PA-RISC library. A PA-RISC shared
167library cannot be loaded into an Itanium executable nor vice-versa.
168
f2a260d6
GS
169To create a shared library, the following steps must be performed:
170
171 1. Compile source modules with +z or +Z flag to create a .o module
172 which contains Position-Independent Code (PIC). The linker will
173 tell you in the next step if +Z was needed.
174
175 2. Link the shared library using the -b flag. If the code calls
176 any functions in other system libraries (e.g., libm), it must
177 be included on this line.
178
179(Note that these steps are usually handled automatically by the extension's
180Makefile).
181
182If these dependent libraries are not listed at shared library creation
183time, you will get fatal "Unresolved symbol" errors at run time when the
184library is loaded.
185
a75f7dba 186You may create a shared library that refers to another library, which
60ed1d8c
GS
187may be either an archive library or a shared library. If this second
188library is a shared library, this is called a "dependent library". The
189dependent library's name is recorded in the main shared library, but it
190is not linked into the shared library. Instead, it is loaded when the
191main shared library is loaded. This can cause problems if you build an
192extension on one system and move it to another system where the
193libraries may not be located in the same place as on the first system.
f2a260d6
GS
194
195If the referred library is an archive library, then it is treated as a
196simple collection of .o modules (all of which must contain PIC). These
197modules are then linked into the shared library.
198
60ed1d8c
GS
199Note that it is okay to create a library which contains a dependent
200library that is already linked into perl.
f2a260d6 201
42be3f00
JH
202Some extensions, like DB_File and Compress::Zlib use/require prebuilt
203libraries for the perl extensions/modules to work. If these libraries
3853ea39
JH
204are built using the default configuration, it might happen that you
205run into an error like "invalid loader fixup" during load phase.
206HP is aware of this problem. Search the HP-UX cxx-dev forums for
207discussions about the subject. The short answer is that B<everything>
208(all libraries, everything) must be compiled with C<+z> or C<+Z> to be
209PIC (position independent code). In HP-UX 11.00 or newer the linker
210error message should tell the name of the offending object file.
42be3f00
JH
211
212A more general approach is to intervene manually, as with an example for
213the DB_File module, which requires SleepyCat's libdb.sl:
214
215 # cd .../db-3.2.9/build_unix
216 # vi Makefile
217 ... add +Z to all cflags to create shared objects
218 CFLAGS= -c $(CPPFLAGS) +Z -Ae +O2 +Onolimit \
219 -I/usr/local/include -I/usr/include/X11R6
220 CXXFLAGS= -c $(CPPFLAGS) +Z -Ae +O2 +Onolimit \
221 -I/usr/local/include -I/usr/include/X11R6
222
223 # make clean
224 # make
225 # mkdir tmp
226 # cd tmp
227 # ar x ../libdb.a
228 # ld -b -o libdb-3.2.sl *.o
229 # mv libdb-3.2.sl /usr/local/lib
230 # rm *.o
231 # cd /usr/local/lib
232 # rm -f libdb.sl
233 # ln -s libdb-3.2.sl libdb.sl
234
235 # cd .../DB_File-1.76
236 # make distclean
237 # perl Makefile.PL
238 # make
239 # make test
240 # make install
241
13e84f2c
JH
242It is no longer possible to link PA-RISC 1.0 shared libraries (even
243though the command-line flags are still present).
244
245PA-RISC and Itanium object files are not interchangeable. Although
246you may be able to use ar to create an archive library of PA-RISC
247object files on an Itanium system, you cannot link against it using
248an Itanium link editor.
f2a260d6
GS
249
250=head2 The HP ANSI C Compiler
251
60ed1d8c
GS
252When using this compiler to build Perl, you should make sure that the
253flag -Aa is added to the cpprun and cppstdin variables in the config.sh
42be3f00
JH
254file (though see the section on 64-bit perl below). If you are using a
255recent version of the Perl distribution, these flags are set automatically.
f2a260d6 256
2be3a552
MB
257=head2 The GNU C Compiler
258
259When you are going to use the GNU C compiler (gcc), and you don't have
260gcc yet, you can either build it yourself from the sources (available
261from e.g. http://www.gnu.ai.mit.edu/software/gcc/releases.html) or fetch
262a prebuilt binary from the HP porting center. There are two places where
263gcc prebuilds can be fetched the first and best (for HP-UX 11 only) is
264http://h21007.www2.hp.com/dspp/tech/tech_TechSoftwareDetailPage_IDX/1,1703,547,00.html
265the second is http://hpux.cs.utah.edu/hppd/hpux/Gnu/ where you can also
266find the GNU binutils package.
267
268Building a 64bit capable gcc from source is possible only when you have
269the HP C-ANSI C compiler available, which you should use anyway when
270building perl.
271
a83b6f46 272=head2 Using Large Files with Perl on HP-UX
f2a260d6 273
60ed1d8c
GS
274Beginning with HP-UX version 10.20, files larger than 2GB (2^31 bytes)
275may be created and manipulated. Three separate methods of doing this
276are available. Of these methods, the best method for Perl is to compile
277using the -Duselargefiles flag to Configure. This causes Perl to be
278compiled using structures and functions in which these are 64 bits wide,
279rather than 32 bits wide. (Note that this will only work with HP's ANSI
280C compiler. If you want to compile Perl using gcc, you will have to get
2be3a552 281a version of the compiler that support 64-bit operations. See above for
f3e4a94e 282where to find it.)
60ed1d8c
GS
283
284There are some drawbacks to this approach. One is that any extension
285which calls any file-manipulating C function will need to be recompiled
f74a9bd3
GS
286(just follow the usual "perl Makefile.PL; make; make test; make install"
287procedure).
60ed1d8c 288
d66be8f9
GS
289The list of functions that will need to recompiled is:
290creat, fgetpos, fopen,
291freopen, fsetpos, fstat,
292fstatvfs, fstatvfsdev, ftruncate,
293ftw, lockf, lseek,
294lstat, mmap, nftw,
295open, prealloc, stat,
296statvfs, statvfsdev, tmpfile,
297truncate, getrlimit, setrlimit
f2a260d6 298
60ed1d8c
GS
299Another drawback is only valid for Perl versions before 5.6.0. This
300drawback is that the seek and tell functions (both the builtin version
301and POSIX module version) will not perform correctly.
302
303It is strongly recommended that you use this flag when you run
304Configure. If you do not do this, but later answer the question about
305large files when Configure asks you, you may get a configuration that
306cannot be compiled, or that does not function as expected.
307
a83b6f46 308=head2 Threaded Perl on HP-UX
f2a260d6 309
c7d9b096
JH
310It is possible to compile a version of threaded Perl on any version of
311HP-UX before 10.30, but it is strongly suggested that you be running on
f2a260d6
GS
312HP-UX 11.00 at least.
313
60ed1d8c
GS
314To compile Perl with threads, add -Dusethreads to the arguments of
315Configure. Verify that the -D_POSIX_C_SOURCE=199506L compiler flag is
316automatically added to the list of flags. Also make sure that -lpthread
42be3f00
JH
317is listed before -lc in the list of libraries to link Perl with. The
318hints provided for HP-UX during Configure will try very hard to get
319this right for you.
f2a260d6 320
210b36aa 321HP-UX versions before 10.30 require a separate installation of a POSIX
c7d9b096
JH
322threads library package. Two examples are the HP DCE package, available
323on "HP-UX Hardware Extensions 3.0, Install and Core OS, Release 10.20,
324April 1999 (B3920-13941)" or the Freely available PTH package, available
325though worldwide HP-UX mirrors of precompiled packages
37a78d01 326(e.g. http://hpux.tn.tudelft.nl/hppd/hpux/)
c7d9b096 327
fa01be49
MB
328If you are going to use the HP DCE package, the library used for threading
329is /usr/lib/libcma.sl, but there have been multiple updates of that
330library over time. Perl will build with the first version, but it
331will not pass the test suite. Older Oracle versions might be a compelling
8e4bcd96 332reason not to update that library, otherwise please find a newer version
fa01be49
MB
333in one of the following patches: PHSS_19739, PHSS_20608, or PHSS_23672
334
335reformatted output:
336
337 d3:/usr/lib 106 > what libcma-*.1
338 libcma-00000.1:
339 HP DCE/9000 1.5 Module: libcma.sl (Export)
340 Date: Apr 29 1996 22:11:24
341 libcma-19739.1:
342 HP DCE/9000 1.5 PHSS_19739-40 Module: libcma.sl (Export)
343 Date: Sep 4 1999 01:59:07
344 libcma-20608.1:
345 HP DCE/9000 1.5 PHSS_20608 Module: libcma.1 (Export)
346 Date: Dec 8 1999 18:41:23
347 libcma-23672.1:
348 HP DCE/9000 1.5 PHSS_23672 Module: libcma.1 (Export)
349 Date: Apr 9 2001 10:01:06
350 d3:/usr/lib 107 >
351
352
a83b6f46 353=head2 64-bit Perl on HP-UX
f2a260d6 354
60ed1d8c
GS
355Beginning with HP-UX 11.00, programs compiled under HP-UX can take
356advantage of the LP64 programming environment (LP64 means Longs and
357Pointers are 64 bits wide).
f2a260d6 358
60ed1d8c
GS
359Work is being performed on Perl to make it 64-bit compliant on all
360versions of Unix. Once this is complete, scalar variables will be able
361to hold numbers larger than 2^32 with complete precision.
f2a260d6
GS
362
363As of the date of this document, Perl is not 64-bit compliant on HP-UX.
364
60ed1d8c
GS
365Should a user wish to experiment with compiling Perl in the LP64
366environment, use the -Duse64bitall flag to Configure. This will force
367Perl to be compiled in a pure LP64 environment (via the +DD64 flag).
f74a9bd3 368
60ed1d8c
GS
369You can also use the -Duse64bitint flag to Configure. Although there
370are some minor differences between compiling Perl with this flag versus
371the -Duse64bitall flag, they should not be noticeable from a Perl user's
372perspective.
f74a9bd3 373
60ed1d8c
GS
374In both cases, it is strongly recommended that you use these flags when
375you run Configure. If you do not use do this, but later answer the
376questions about 64-bit numbers when Configure asks you, you may get a
377configuration that cannot be compiled, or that does not function as
378expected.
f74a9bd3 379
60ed1d8c
GS
380(Note that these Configure flags will only work with HP's ANSI C
381compiler. If you want to compile Perl using gcc, you will have to get a
382version of the compiler that support 64-bit operations.)
f2a260d6 383
a83b6f46 384=head2 GDBM and Threads on HP-UX
d66be8f9 385
60ed1d8c
GS
386If you attempt to compile Perl with threads on an 11.X system and also
387link in the GDBM library, then Perl will immediately core dump when it
388starts up. The only workaround at this point is to relink the GDBM
389library under 11.X, then relink it into Perl.
d66be8f9 390
a83b6f46 391=head2 NFS filesystems and utime(2) on HP-UX
d66be8f9
GS
392
393If you are compiling Perl on a remotely-mounted NFS filesystem, the test
60ed1d8c
GS
394io/fs.t may fail on test #18. This appears to be a bug in HP-UX and no
395fix is currently available.
d66be8f9 396
a83b6f46 397=head2 perl -P and // and HP-UX
183968aa 398
efdf3af0 399In HP-UX Perl is compiled with flags that will cause problems if the
183968aa
MH
400-P flag of Perl (preprocess Perl code with the C preprocessor before
401perl sees it) is used. The problem is that C<//>, being a C++-style
402until-end-of-line comment, will disappear along with the remainder
403of the line. This means that common Perl constructs like
404
efdf3af0 405 s/foo//;
183968aa
MH
406
407will turn into illegal code
408
efdf3af0 409 s/foo
183968aa 410
efdf3af0
JH
411The workaround is to use some other quoting separator than C<"/">,
412like for example C<"!">:
183968aa 413
efdf3af0 414 s!foo!!;
183968aa 415
a83b6f46 416=head2 HP-UX Kernel Parameters (maxdsiz) for Compiling Perl
13e84f2c
JH
417
418By default, HP-UX comes configured with a maximum data segment size of
41964MB. This is too small to correctly compile Perl with the maximum
420optimization levels. You can increase the size of the maxdsiz kernel
421parameter through the use of SAM.
422
423When using the GUI version of SAM, click on the Kernel Configuration
424icon, then the Configurable Parameters icon. Scroll down and select
425the maxdsiz line. From the Actions menu, select the Modify Configurable
426Parameter item. Insert the new formula into the Formula/Value box.
427Then follow the instructions to rebuild your kernel and reboot your
428system.
429
430In general, a value of 256MB (or "256*1024*1024") is sufficient for
431Perl to compile at maximum optimization.
432
1081c3b9
JH
433=head1 nss_delete core dump from op/pwent or op/grent
434
435You may get a bus error core dump from the op/pwent or op/grent
436tests. If compiled with -g you will see a stack trace much like
437the following:
438
439 #0 0xc004216c in () from /usr/lib/libc.2
440 #1 0xc00d7550 in __nss_src_state_destr () from /usr/lib/libc.2
441 #2 0xc00d7768 in __nss_src_state_destr () from /usr/lib/libc.2
442 #3 0xc00d78a8 in nss_delete () from /usr/lib/libc.2
443 #4 0xc01126d8 in endpwent () from /usr/lib/libc.2
444 #5 0xd1950 in Perl_pp_epwent () from ./perl
445 #6 0x94d3c in Perl_runops_standard () from ./perl
446 #7 0x23728 in S_run_body () from ./perl
447 #8 0x23428 in perl_run () from ./perl
448 #9 0x2005c in main () from ./perl
449
450The key here is the C<nss_delete> call. One workaround for this
451bug seems to be to create add to the file F</etc/nsswitch.conf>
452(at least) the following lines
453
454 group: files
455 passwd: files
456
457Whether you are using NIS does not matter. Amazingly enough,
458the same bug affects also Solaris.
459
f2a260d6
GS
460=head1 AUTHOR
461
462Jeff Okamoto <okamoto@corp.hp.com>
fa01be49 463H.Merijn Brand <h.m.brand@hccnet.nl>
f2a260d6
GS
464
465With much assistance regarding shared libraries from Marc Sabatella.
466
467=head1 DATE
468
fa01be49 469Version 0.6.5: 2002-02-27
f2a260d6
GS
470
471=cut