diff options
author | Andy Dougherty <doughera@lafayette.edu> | 2002-12-02 07:04:40 -0500 |
---|---|---|
committer | H.Merijn Brand <h.m.brand@xs4all.nl> | 2002-12-02 16:00:12 +0000 |
commit | b48c3bfbb4a90d003ead63cb81cdf4e84295c8b9 (patch) | |
tree | ad636edbc4b2b64fd2337bb4f701a916b46bfafe /README.hpux | |
parent | 17aa7f3df185d8eaf8e0b1dad106f97ac3c6da48 (diff) | |
download | perl-b48c3bfbb4a90d003ead63cb81cdf4e84295c8b9.tar.gz |
Re: [perl #15129] building a dynamically linked Perl 5.6.1 on HPUX 11.0
Message-ID: <Pine.SOL.4.10.10212021200050.24023-100000@maxwell.phys.lafayette.edu>
p4raw-id: //depot/perl@18231
Diffstat (limited to 'README.hpux')
-rw-r--r-- | README.hpux | 6 |
1 files changed, 4 insertions, 2 deletions
diff --git a/README.hpux b/README.hpux index b0536dc5c5..ade330948f 100644 --- a/README.hpux +++ b/README.hpux @@ -68,7 +68,7 @@ difficulty, but also can take advantage of features listed later that 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 @@ To create a shared library, the following steps must be performed: 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 @@ run into an error like "invalid loader fixup" during load phase. 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 |