Remedy does not ship the ARS API libraries in HP-UX "sl" format (shame on
them) meaning anything linked with those libraries must be statically
linked. For Perl, that means the ARS extension cannot be dynamically loaded.
All is not lost, however, try the following:
1) Copy or move the ARSperl directory to .../<perl_source_directory>/ext
which is where you will find POSIX, FCNTL etc.
2) For convenience, rename the ARSperl directory ARS (so it is consistent with
the naming of the other Perl extensions).
3) change directories to the main perl source directory.
4) Re-run Configure. When it asks you which extensions you want statically
linked, specify ARS.
5) Follow the rest of the standard Perl build procedures.
What you *should* end up with is Perl 5 with the ARS extensions built into
the main perl executable, not as a dynamically loaded extension. This makes
the perl executable somewhat larger than a "pure" perl executable but is in
no way harmful. All other "stock" Perl scripts should run without incident.
At least everything works just fine on my systems (plural).
For the record: I'm on K-100 boxes under HP-UX 10.01 with Perl 5.002 and HP C
(the one you have to pay extra for - not the emasculated version that ships as
part of the base OS). ARS version is 2.0.2.
YMMV
At 04:09 AM 07/19/96 -0400, Bryan Mawhinney wrote:
>
>Hello folks,
>
>I was wondering whether anyone had any success building ARSperl under
>HP-UX?
>
>During the link phase, I get the following error
>
>/usr/bin/ld: DP-Relative Code in file
>/opt/remedy/ars/api/lib/libar.a(ar.o) - Sh
>ared Library must be Position-Independent
>
>I'm still new to this kind of thing, but I guess this means I'm stuffed.
> I don't have the source to ar.o, so I can't recompile it to use PIC
>code.
>
>Perhaps I could recompile perl with the ARS stuff linked in statically,
>but that doesn't sound particularly attractive.
>
>For the record, I'm using HP-UX10.01, ARS v2.0.2, Perl 5.003, and GCC
>2.7.2
>
>TIA
>
> Bryan
>
>
>
--
Bill Meahan wm...@fo...
Ford Motor Company -- End User Support - North America
Not an official statement of Ford Motor Company or anyone else
except the author.
|
