Title: Message
    Yes but for some reason d2i_x509 is not exported by ssleay32 nor libeay32.lib. That is what I'm trying to figure out. I link with both of the libraries and call d2i_x509 in one of my methods and during linking I get a undefined symbol for d2i_x509
 
- Andrew
-----Original Message-----
From: Greg Stark [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, August 28, 2001 4:09 PM
To: [EMAIL PROTECTED]
Subject: Re: SSLEAY32

The library names are different for the win32 build. They are libeay32.lib and ssleay32.lib.
 
====================
Greg Stark
[EMAIL PROTECTED]
====================
 
 
----- Original Message -----
Sent: Tuesday, August 28, 2001 3:40 PM
Subject: SSLEAY32



        I have come across a problem I'm not quite sure how to fix. I use d2i_x509 in one of my applications. When I compile on NT I can't find any libssl.lib or libcrypto.lib files all I find is ssleay32.lib so I link against that. It comes up with an undefined symbol _d2i_x509. But if I compile on solaris and link against libssl.so and libcrytp.so it compiles. Why is there a different between the two platforms?

-------------------------------------
Andrew T. Finnell
Software Engineer
eSecurity Inc
(321) 394-2485

Reply via email to