require the use of HP compiler-specific command-line flags.
If you decide to use gcc, make sure your installation is recent and
-complete, and be sure to read the Perl README file for more gcc-specific
+complete, and be sure to read the Perl INSTALL file for more gcc-specific
details.
=head2 PA-RISC
D280, D370, D380, D390, D650, J220, J2240, J280, J282, J400, J410,
J5000, J5500XM, J5600, J7000, J7600, K250, K260, K260-EG, K270, K360,
K370, K380, K450, K460, K460-EG, K460-XP, K470, K570, K580, L1000,
- L2000, L3000, N4000, R380, R390, RP2400, RP2430, RP2450, RP2470,
- RP5400, RP5430, RP5450, RP5470, RP7400, RP7410, RP8400, SD16000,
- SD32000, SD64000, T540, T600, V2000, V2200, V2250, V2500, V2600
+ L2000, L3000, N4000, R380, R390, RP2400, RP2405, RP2430, RP2450,
+ RP2470, RP5400, RP5405, RP5430, RP5450, RP5470, RP7400, RP7405,
+ RP7410, RP8400, SD16000, SD32000, SD64000, T540, T600, V2000, V2200,
+ V2250, V2500, V2600
Just before HP took over Compaq, some systems were renamed. Visit
http://www.hp.com/products1/servers/server_names.html to see what
the changes are, or will be.
HP 9000 A-Class servers, now renamed HP Server rp2400 series.
- HP 9000 N-Class servers, now renamed HP Server rp7400.
HP 9000 L-Class servers, now renamed HP Server rp5400 series.
+ HP 9000 N-Class servers, now renamed HP Server rp7400.
=head2 Itanium
1. Compile source modules with +z or +Z flag to create a .o module
which contains Position-Independent Code (PIC). The linker will
tell you in the next step if +Z was needed.
+ (For gcc, the appropriate flag is -fpic or -fPIC.)
2. Link the shared library using the -b flag. If the code calls
any functions in other system libraries (e.g., libm), it must
HP is aware of this problem. Search the HP-UX cxx-dev forums for
discussions about the subject. The short answer is that B<everything>
(all libraries, everything) must be compiled with C<+z> or C<+Z> to be
-PIC (position independent code). In HP-UX 11.00 or newer the linker
+PIC (position independent code). (For gcc, that would be
+C<-fpic> or C<-fPIC>). In HP-UX 11.00 or newer the linker
error message should tell the name of the offending object file.
A more general approach is to intervene manually, as with an example for