On Dec 8, 1:58pm, Don Harrop wrote:
> Ok, I finally got it to finish compiling and did a make install. I had to
> change one of the Makefile parameters..
>
> LINKTYPE = dynamic -=> LINKTYPE = static
In which package's Makefile did you change this parameter? Was it in
Net:SSLeay or was it in the library (that Net:SSLeay needs to link
against) that you were fighting with the other day?
> Anyway it finishes the link and then I do a make install but when I run
> perl -e 'use Net::SSLeay' it can't find the SSLeay object.. What gives?
> :-/ Why didn't make install put it in a path that perl could find? I'm a
> little ignorant on how perl's file structure... where extra modules are
> supposed to go and what file names it needs to find. Teach me oh great
> ones.. just don't tell me to wax on/wax off or paint the fence.. :-)
The question I asked above is important because Perl needs to be
able to dynamically load (via dlopen() or the like) the extension
modules.
In my opinion, you should probably have left the LINKTYPE as dynamic.
The library that you mentioned the other day needs to be a shared
object compiled to be PIC to work.
(Of course, I could be entirely wrong. It's been a while since I've
done any substantial amount of work on an HP system.)
Kevin
From Don Harrop <
don@nis4u.com> Fri Dec 8 21:26:23 2000
From: Don Harrop <
don@nis4u.com> (Don Harrop)
Date: Fri, 8 Dec 2000 14:26:23 -0700 (MST)
Subject: HPUX and Net::SSLeay
In-Reply-To: <
14897.20178.777925.917165@owmyeye.ugive.com>
Message-ID: <
Pine.LNX.4.21.0012081424080.8193-100000@tech1.nis4u.com>
Well, I just looked at one of my linux boxes that I've got it running on
and found that there is a file called SSLeay.so in place that is not on
the HPUX boxes.. Maybe changing the link options to static wasn't that
great of an idea after all....
On Fri, 8 Dec 2000
sinck@ugive.com wrote:
>
>
> \_ Anyway it finishes the link and then I do a make install but when I run
> \_ perl -e 'use Net::SSLeay' it can't find the SSLeay object.. What gives?
> \_ :-/ Why didn't make install put it in a path that perl could find? I'm a
> \_ little ignorant on how perl's file structure... where extra modules are
> \_ supposed to go and what file names it needs to find. Teach me oh great
> \_ ones.. just don't tell me to wax on/wax off or paint the fence.. :-)
>
> figure out where it actually got installed...
>
> find / -name SSLeay.pm -print
>
> then
>
> perl -e 'print join("\n", @INC)' ;
>
> and see if the path looks similar.
>
> if not [expected], at the start of your perl scripts, try:
>
> use lib '/some/other/path/lib/perl';
>
> or if that borks,
>
> BEGIN
> {
> unshift (@INC, '/some/other/path/lib/perl');
> }
>
> If all that fails, go find a chicken, a knife, and email me for further
> instructions.
>
> David
>
> ________________________________________________
> See http://PLUG.phoenix.az.us/navigator-mail.shtml if your mail doesn't post to the list quickly and you use Netscape to write mail.
>
> Plug-discuss mailing list - Plug-discuss@lists.PLUG.phoenix.az.us
> http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
>
(text/plain)