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:
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, cx2600, rx1600, rx1620, rx2600, rx2600hptc, rx2620, rx3600,
+ rx4610, rx4640, rx5670, rx6600, rx7620, rx8620, rx8640, rx9610
To see all about your machine, type
has changed the configuration process to add +z on HP-UX automatically.
# cd .../db-4.2.25/build_unix
- # env CFLAGS=+DA2.0w LDFLAGS=+DA2.0w ../dist/configure
+ # env CFLAGS=+DD64 LDFLAGS=+DD64 ../dist/configure
should work to generate 64bit shared libraries for HP-UX 11.00 and 11i.
file (though see the section on 64-bit perl below). If you are using a
recent version of the Perl distribution, these flags are set automatically.
+Even though HP-UX 10.20 and 11.00 are not actively maintained by HP
+anymore, updates for the HP ANSI C compiler are still available from
+time to time, and it might be advisable to see if updates are applicable.
+At the moment of writing, the latests available patches for 11.00 that
+should be applied are PHSS_35098, PHSS_35175, PHSS_35100, PHSS_33036,
+and PHSS_33902). If you have a SUM account, you can use it to search
+for updates/patches. Enter "ANSI" as keyword.
+
=head2 The GNU C Compiler
When you are going to use the GNU C compiler (gcc), and you don't have
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.
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
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
=head1 DATE
-Version 0.7.3: 2005-03-08
+Version 0.7.8: 2006-10-10
=cut
https://perl5.git.perl.org / perl5.git / blobdiff