OpenSSL Support; 

    While waiting for the 0.9.8zb version to be released, I tried the latest 
snapshot from ftp://ftp.openssl.org/snapshot/ 
openssl-0.9.8-stable-SNAP-20140611.tar.gz and got the exact same results.  I'm 
kind of dead in the water until I can compile, can you offer any advice?  Thank 
you.

-----Original Message-----
From: The default queue via RT [mailto:[email protected]] 
Sent: Tuesday, June 10, 2014 2:54 PM
To: Swenson, Ken_S. (IS)
Subject: EXT :[openssl.org #3395] AutoReply: Can’t Compile 0.9.8za FIPS on Win 
7 32 Bit w/ Visual Studio 2010.


Greetings,

This message has been automatically generated in response to the creation of a 
trouble ticket regarding:
        "Can’t Compile 0.9.8za FIPS on Win 7 32 Bit w/ Visual Studio 2010.", a 
summary of which appears below.

There is no need to reply to this message right now.  Your ticket has been 
assigned an ID of [openssl.org #3395].

Please include the string:

         [openssl.org #3395]

in the subject line of all future correspondence about this issue. To do so, 
you may reply to this message.

                        Thank you,
                        [email protected]

-------------------------------------------------------------------------
 
OpenSSL Support;

    I issued the command ms\do_fips (also tried w/ ‘no-ec’ option,) it compiles 
for about 5 minutes, and then throws this error…
 
 
Creating library tmp32dll\junk.lib and object tmp32dll\junk.exp
 
fipscanister.lib(rsa_oaep.obj) : error LNK2019: unresolved external symbol 
_CRYPTO_memcmp referenced in function _RSA_padding_check_PKCS1_OAEP
 
out32dll\fips_test_suite.exe : fatal error LNK1120: 1 unresolved externals
 
First stage Link failure at util\fipslink.pl line 42.
 
NMAKE : fatal error U1077: 'C:\Perl\bin\perl.EXE' : return code '0x60'
 
Stop.

______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
Development Mailing List                       [email protected]
Automated List Manager                           [email protected]

Reply via email to