RE: Problem with installing Crypt::SSLeay

2001-11-02 Thread Feng, James
Josh, Thanks. After I installed gcc3, I have successfully installed SSLeay. Thanks again. > -Original Message- > From: Joshua Chamas [mailto:[EMAIL PROTECTED]] > Sent: Thursday, November 01, 2001 1:57 PM > To: Feng, James > Cc: [EMAIL PROTECTED]; Keary Suska > Subject

Re: Problem with installing Crypt::SSLeay

2001-10-31 Thread Keary Suska
44:19 +1100 > To: <[EMAIL PROTECTED]> > Subject: RE: Problem with installing Crypt::SSLeay > > Looks like your loader can't find "libgcc_s.so.1" which is used by > "SSLeay.so", make a sym link to a lib path that it will look in (like > "

RE: Problem with installing Crypt::SSLeay

2001-10-31 Thread Mark Strong
m: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Feng, James Sent: Thursday, 1 November 2001 7:49 To: Keary Suska Cc: [EMAIL PROTECTED] Subject: RE: Problem with installing Crypt::SSLeay Hi Keary, After I recompiled perl 5.6.1, I installed modules, URI, MIME-Base64, HTML-Parser, libnet

Re: Problem with installing Crypt::SSLeay

2001-10-31 Thread Joshua Chamas
"Feng, James" wrote: > > Hi Keary, > > After I recompiled perl 5.6.1, I installed modules, URI, MIME-Base64, > HTML-Parser, libnet and Digest-MD5, then I installed libwww-perl. When I > tried to install SSLeay, at the point of 'make test' I still got the > error I previously got but this time I

RE: Problem with installing Crypt::SSLeay

2001-10-31 Thread Feng, James
haps you forgot to load "LWP::Protocol::https"?) > -Original Message- > From: Keary Suska [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, October 31, 2001 1:26 PM > To: [EMAIL PROTECTED]; Feng, James > Subject: Re: Problem with installing Crypt::SSLeay > > > It appears th

Re: Problem with installing Crypt::SSLeay

2001-10-31 Thread Keary Suska
It appears that the SSLeay loadable is not being created: 'blib/arch/auto/Crypt/SSLeay/SSLeay.so' If this file isn't there, try just running 'make' and look again. You could also do a 'find' in the source tree to see if it is being created elsewhere, but it shouldn't. Perhaps the makfile isn't