Change 18231 by merijn@merijn-l1 on 2002/12/02 16:00:12
Subject: Re: [perl #15129] building a dynamically linked Perl 5.6.1 on HPUX
11.0
Date: Mon, 2 Dec 2002 12:04:40 -0500 (EST)
From: Andy Dougherty <[EMAIL PROTECTED]>
Message-ID:
<[EMAIL PROTECTED]>
Affected files ...
.... //depot/perl/README.hpux#39 edit
Differences ...
==== //depot/perl/README.hpux#39 (text) ====
Index: perl/README.hpux
--- perl/README.hpux#38~17888~ Tue Sep 10 02:20:52 2002
+++ perl/README.hpux Mon Dec 2 08:00:12 2002
@@ -68,7 +68,7 @@
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
@@ -203,6 +203,7 @@
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
@@ -238,7 +239,8 @@
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
End of Patch.
