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