X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=blobdiff_plain;f=README.hpux;h=bd9757511c3d46fe966c69beb99df2e162bbad2a;hb=51254d33a14eeacb273f244a97f13b86d9e56aa2;hp=7c52492a589cb42ac3d885b8b86d1dbed831cfa3;hpb=3bd76f0a957f9db1d7e0dc7f797f6ef163db655c;p=p5sagit%2Fp5-mst-13.2.git diff --git a/README.hpux b/README.hpux index 7c52492..bd97575 100644 --- a/README.hpux +++ b/README.hpux @@ -162,9 +162,9 @@ that contained the explanation is dead, so here's a short summary: HP 9000 L-Class servers, now renamed HP Server rp5400 series. HP 9000 N-Class servers, now renamed HP Server rp7400. - rp2400, rp2405, rp2430, rp2450, rp2470, rp3410, rp3440, rp4440, - rp5400, rp5405, rp5430, rp5450, rp5470, rp7400, rp7405, rp7410, - rp7420, rp8400, rp8420, Superdome + rp2400, rp2405, rp2430, rp2450, rp2470, rp3410, rp3440, rp4410, + rp4440, rp5400, rp5405, rp5430, rp5450, rp5470, rp7400, rp7405, + rp7410, rp7420, rp8400, rp8420, Superdome The current naming convention is: @@ -206,8 +206,8 @@ HP also ships servers with the 128-bit Itanium processor(s). As of the date of this document's last update, the following systems contain Itanium or Itanium 2 chips (this is very likely to be out of date): - rx1600, rx1620, rx2600, rx2600hptc, rx2620, rx4610, rx4640, rx5670, - rx7620, rx8620, rx9610 + BL60p, rx1600, rx1620, rx2600, rx2600hptc, rx2620, rx4610, rx4640, + rx5670, rx7620, rx8620, rx9610 To see all about your machine, type @@ -352,7 +352,7 @@ on that page to rebuild gcc using itself. On PA-RISC you need a different compiler for 32-bit applications and for 64-bit applications. On PA-RISC, 32-bit objects and 64-bit objects do -not mix. period. There is no different behaviour for HP C-ANSI-C or GNU +not mix. Period. There is no different behaviour for HP C-ANSI-C or GNU gcc. So if you require your perl binary to use 64-bit libraries, like Oracle-64bit, you MUST build a 64-bit perl. @@ -414,8 +414,7 @@ HP-UX versions before 10.30 require a separate installation of a POSIX threads library package. Two examples are the HP DCE package, available on "HP-UX Hardware Extensions 3.0, Install and Core OS, Release 10.20, April 1999 (B3920-13941)" or the Freely available PTH package, available -though worldwide HP-UX mirrors of precompiled packages -(e.g. http://hpux.tn.tudelft.nl/hppd/hpux/) +on H.Merijn's site (http://mirrors.develooper.com/hpux/). If you are going to use the HP DCE package, the library used for threading is /usr/lib/libcma.sl, but there have been multiple updates of that @@ -441,33 +440,43 @@ reformatted output: Date: Apr 9 2001 10:01:06 d3:/usr/lib 107 > +If you choose for the PTH package, use swinstall to install pth in +the default location (/opt/pth), and then make symbolic links to the +libraries from /usr/lib + + # cd /usr/lib + # ln -s /opt/pth/lib/libpth* . + +For building perl to support Oracle, it needs to be linked with libcl +and libpthread. So even if your perl is an unthreaded build, these +libraries might be required. See "Oracle on HP-UX" below. =head2 64-bit Perl on HP-UX Beginning with HP-UX 11.00, programs compiled under HP-UX can take advantage of the LP64 programming environment (LP64 means Longs and -Pointers are 64 bits wide). - -Work is being performed on Perl to make it 64-bit compliant on all -versions of Unix. Once this is complete, scalar variables will be able -to hold numbers larger than 2^32 with complete precision. +Pointers are 64 bits wide), in which scalar variables will be able +to hold numbers larger than 2^32 with complete precision. Perl has +proven to be consistent and reliable in 64bit mode since 5.8.1 on +all HP-UX 11.xx. As of the date of this document, Perl is fully 64-bit compliant on HP-UX 11.00 and up for both cc- and gcc builds. If you are about to build a 64-bit perl with GNU gcc, please read the gcc section carefully. -Should a user wish to experiment with compiling Perl in the LP64 -environment, use the -Duse64bitall flag to Configure. This will force -Perl to be compiled in a pure LP64 environment (with the +DD64 flag for -HP C-ANSI-C, with no additional options for GNU gcc 64-bit on PA-RISC, -and with -mlp64 for GNU gcc on Itanium). +Should a user have the need for compiling Perl in the LP64 environment, +use the -Duse64bitall flag to Configure. This will force Perl to be +compiled in a pure LP64 environment (with the +DD64 flag for HP C-ANSI-C, +with no additional options for GNU gcc 64-bit on PA-RISC, and with +-mlp64 for GNU gcc on Itanium). If you want to compile Perl using gcc, you will have to get a version of the compiler that supports 64-bit operations.) You can also use the -Duse64bitint flag to Configure. Although there are some minor differences between compiling Perl with this flag versus the -Duse64bitall flag, they should not be noticeable from a Perl user's -perspective. +perspective. When configuring -Duse64bitint using a 64bit gcc on a +pa-risc architecture, -Duse64bitint is silently promoted to -Duse64bitall. In both cases, it is strongly recommended that you use these flags when you run Configure. If you do not use do this, but later answer the @@ -577,6 +586,6 @@ With much assistance regarding shared libraries from Marc Sabatella. =head1 DATE -Version 0.7.3: 2005-03-08 +Version 0.7.6: 2005-12-20 =cut