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