Dr. Stephen,

Thanks for your reply. After changing to what you have mentioned I am getting 
this security error during linking.


===Error log ===
C:\openssl-0.9.8j>nmake -f ms\nt.mak

Microsoft (R) Program Maintenance Utility   Version 7.00.8882
Copyright (C) Microsoft Corp 1988-2000. All rights reserved.

Building OpenSSL
        cl /Fotmp32\fips_standalone_sha1.obj -Iinc32 -Itmp32 /MD /Ox /O2 /Ob2 /W
3 /WX /Gs0 /GF /Gy /nologo -DOPENSSL_SYSNAME_WIN32 -DWIN32_LEAN_AND_MEAN -DL_END
IAN -DDSO_WIN32 -D_CRT_SECURE_NO_DEPRECATE -D_CRT_NONSTDC_NO_DEPRECATE /Fdout32
-DOPENSSL_NO_CAMELLIA -DOPENSSL_NO_SEED -DOPENSSL_NO_RC5 -DOPENSSL_NO_MDC2 -DOPE
NSSL_NO_CMS -DOPENSSL_NO_JPAKE -DOPENSSL_NO_CAPIENG -DOPENSSL_NO_KRB5 -DOPENSSL_
FIPS -DOPENSSL_NO_DYNAMIC_ENGINE /Zl  -c .\fips\sha\fips_standalone_sha1.c
fips_standalone_sha1.c
        link /nologo /subsystem:console /opt:ref /out:out32\fips_standalone_sha1
.exe @C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\1\nm137.tmp
fips_standalone_sha1.obj : error LNK2019: unresolved external symbol __security_
cookie referenced in function .hmac_init
fips_standalone_sha1.obj : error LNK2019: unresolved external symbol .__security
_check_cookie referenced in function .hmac_init
out32\fips_standalone_sha1.exe : fatal error LNK1120: 2 unresolved externals
NMAKE : fatal error U1077: 'link' : return code '0x460'
Stop.

============

Thanks,
Justin

--- On Tue, 1/13/09, Dr. Stephen Henson <st...@openssl.org> wrote:
From: Dr. Stephen Henson <st...@openssl.org>
Subject: Re: Problem building Openssl-0.9.8j with fips
To: openssl-users@openssl.org
Date: Tuesday, January 13, 2009, 3:05 AM

On Mon, Jan 12, 2009, Justin A wrote:

> 
> Hi All,
> 
> I am getting this error ( below)  while building fips capable  OpenSSL
on version 0.9.8j on WIN-IA64  showing possible loss of data and bails out.
> 
> 1) I did NOT have any issues building the fips - 1.2 ( fipscanister build
- FIPS MODULE ) on the same environment.
> 2) When building the fips capable openSSL on version 0.9.8j  I am running
into error as shown below.
> 
> Command I used to run the fips-capable openSSL is    
> 
> C:\openssl-0.9.8j>perl Configure VC-WIN64I fips no-asm
--with-fipslibdir=C:\FIPS\openssl-fips-1.2\out32dll
> 
> C:\openssl-0.9.8j>ms\do_ms
> 
> C:\openssl-0.9.8j>nmake -f ms\nt.mak
> 
> 
> 
> Error log
> =========
> Copying: ./ssl/dtls1.h to inc32/openssl/dtls1.h
>         perl util/copy.pl ".\ssl\kssl.h"
"inc32\openssl\kssl.h"
> Copying: ./ssl/kssl.h to inc32/openssl/kssl.h
>         cl /Fotmp32\fips_standalone_sha1.obj -Iinc32 -Itmp32
/MD /Ox /O2 /Ob2 /W
> 3 /WX /Gs0 /GF /Gy /nologo -DOPENSSL_SYSNAME_WIN32 -DWIN32_LEAN_AND_MEAN
-DL_END
> IAN -DDSO_WIN32 -D_CRT_SECURE_NO_DEPRECATE -D_CRT_NONSTDC_NO_DEPRECATE
/Fdout32
> -DOPENSSL_NO_CAMELLIA -DOPENSSL_NO_SEED -DOPENSSL_NO_RC5 -DOPENSSL_NO_MDC2
-DOPE
> NSSL_NO_CMS -DOPENSSL_NO_JPAKE -DOPENSSL_NO_CAPIENG -DOPENSSL_NO_KRB5
-DOPENSSL_
> FIPS -DOPENSSL_NO_DYNAMIC_ENGINE /Zl  -c
.\fips\sha\fips_standalone_sha1.c
> fips_standalone_sha1.c
> fips\sha\fips_standalone_sha1.c(68) : error C2220: warning treated
as error - no
>  'object' file generated
> fips\sha\fips_standalone_sha1.c(68) : warning C4267:
'initializing' : conversion
>  from 'size_t' to 'int', possible loss of data
> fips\sha\fips_standalone_sha1.c(142) : warning C4267:
'initializing' : conversio
> n from 'size_t' to 'int', possible loss of data
> NMAKE : fatal error U1077: 'cl' : return code '0x2'
> Stop.
> 
> ===========================
> 
> Appreciate your help on this one..!!!
> 

Try changing the two "int" declarations on those lines to size_t.

Let me know if you get any other warnings later on.

Steve.
--
Dr Stephen N. Henson. Email, S/MIME and PGP keys: see homepage
OpenSSL project core developer and freelance consultant.
Homepage: http://www.drh-consultancy.demon.co.uk
______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
User Support Mailing List                    openssl-users@openssl.org
Automated List Manager                           majord...@openssl.org



      

Reply via email to