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