Compiling Crypt::SSLeay 0.0.7 with MS VC++ (cl -v says, "Version
11.00", Windows start menu says Microsoft Visual C++ 5).  I'm running
Windows 98, which might be the cause of some of these spurious
problems.

------------------------------------------------------
0
------------------------------------------------------
First compile OpenSSL.  I used a recent snapshot that compiled perfectly.
(openssl-SNAP-19990314-0330)

------------------------------------------------------
1
------------------------------------------------------
Crypt::SSLeay: remove the library test in makefile.pl.

I added a "goto skip;" at the top after the "use" statements and "skip:;"
right before the WriteMakefile() line.

Manually add the INC line to Makefile.pl with the path to your include
libraries from the OpenSSL compilation.

    INC     => "-IC:/Perl/local/openssl-SNAP-19990314-0330/inc32/",

I left the LIBS line alone:

run `perl makefile.pl` to create the Makefile.

------------------------------------------------------
2
------------------------------------------------------

Manually add the 3 ssl libraries to Crypt::SSLeay Makefile.  I couldn't get
makefile.pl to write the libraries correctly to the created Makefile.  I
added them to the EXTRALIBS and LDLOADLIBS lines.  You probably want to use
the path to the output of Your compilation in step 0.  :-)

"C:/Perl/local/openssl-SNAP-19990314-0330/out32dll/libeay32.lib"
"C:/Perl/local/openssl-SNAP-19990314-0330/out32dll/RSAglue.lib"
"C:/Perl/local/openssl-SNAP-19990314-0330/out32dll/ssleay32.lib"

Crypt::SSleay makefile: "suspicious line 735".  There is a tab on line that
might need to be removed.  Between the "pm_to_blib:" section and the
"$(PM_TO_BLIB)" is a tab character inserted by the Makefile maker.

(This may or may not be a real problem.) 

------------------------------------------------------ 
3
------------------------------------------------------ 

Fix reserved words in openssl ssl.h and bn.h function prototype
headers.  My system needs the same fix for older versions of ssleay.
(Back to SSLeay-0.9.0b at least.)  Since you already compiled
openssl, and we are only changing function prototypes, this should
have no effect on Crypt::SSLeay.

I don't know why the C compiler complains about these reserved words when
compiling SSLeay/OpenSSL suite compiles, but it does.
------------------------------------------------------

ssl.h:
('list')
void SSL_set_client_CA_list(SSL *s, STACK *list);
->
void SSL_set_client_CA_list(SSL *s, STACK *list_x);

('list')
void SSL_CTX_set_client_CA_list(SSL_CTX *ctx, STACK *list);
->
void SSL_CTX_set_client_CA_list(SSL_CTX *ctx, STACK *list_x);

('mod')
bn.h:
 BIGNUM *mod; /* just a reference */
->
 BIGNUM *mod_x; /* just a reference */

('mod')
BN_BLINDING *BN_BLINDING_new(BIGNUM *A,BIGNUM *Ai,BIGNUM *mod);
->
BN_BLINDING *BN_BLINDING_new(BIGNUM *A,BIGNUM *Ai,BIGNUM *mod_x);

('na')
void bn_mul_normal(BN_ULONG *r,BN_ULONG *a,int na,BN_ULONG *b,int nb);
->
void bn_mul_normal(BN_ULONG *r,BN_ULONG *a,int na_x,BN_ULONG *b,int nb);

------------------------------------------------------
4
------------------------------------------------------

copy the openssl libraries to somewhere on your path.  (or your perl5lib
path -- i have my lib directory on both for now.)

------------------------------------------------------
"nmake" should now compile Crypt::SSLeay
"nmake install" installs the library.

now if you use 

new HTTP::Request('GET', "https://www.foo.com/"); 

the LWP library will automatically use the SSL libraries.

a simple test downloading a secure page worked for me.

-jack


______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
User Support Mailing List                    [EMAIL PROTECTED]
Automated List Manager                           [EMAIL PROTECTED]

Reply via email to