Hi Guys, I hope this is the right forum for these questions... And I apologise if the answers are obvious, they aren't obvious to me - yet.
I've been using openssl-0.9.8-fips-test-SNAP-20080826.tar.gz </snapshot/openssl-0.9.8-fips-test-SNAP-20080826.tar.gz> for a couple of days. Attempting to pair it with openssl-0.9.8-stable-SNAP-20080826.tar.gz </snapshot/openssl-0.9.8-stable-SNAP-20080826.tar.gz> to create a full build to a set of static libraries. I'm attempting to build both for Win32 using VC6, and for Win64A using MS Server 2003 SDK R2 cross-compiler. I have a couple of comments/questions... The Win32 build now uses nasm instead of the older non-FIPS builds which used masm. Unfortunately the latest nasm distribution that I could find (v2.03.01 from http://sourceforge.net/project/showfiles.php?group_id=6208) has nasm.exe not nasmw.exe in the Win32 distribution. The ms\do_fips sequence calls nasmw.exe. Renaming nasm.exe to nasmw.exe enabled the FIPS build to work, however it might be worth altering the scripts to use nasm.exe not nasmw.exe? Or have I missed something in the config somewhere? Now I think I have a FIPs canister to use. So I moved on to build the latest stable build and link it in. When building the full stable build using... perl Configure no-idea no-rc5 no-krb5 VC-WIN32 fips --with-fipslibdir=..\delivery_w32 ... I get the following warning: "target already defined - VC-WIN32 (offending arg: fips)" ...which may have some bearing on the Win64 build problems below. The build appears to have worked, although I haven't tested it yet. As I'm working on the scripting of the builds I moved on to the Win64 platform using the Retail environment command prompt from the SDK. I'm attempting to build for Win64A using the following Configure sequence... perl Configure fipscanisterbuild VC-WIN64A ...however it seems to configure for Win32 building instead. For instance the invocation of nasm still uses Win32 definitions. The C compilations have WIN32 defined. Again, have I missed something obvious? Why is "fips" in all its guises forcing Win32 behaviour? Regards, Simon Edwards Communications Software Development Micro Focus [EMAIL PROTECTED] The Lawn, 22-30 Old Bath Road Newbury, Berkshire, RG14 1QN, UK Direct: +44 1635 565487 Mobile : +44 7970988817 Fax: +44 1635 33966 Please consider the environment before printing this e-mail. Micro Focus Limited is registered in England and Wales. Registered number: 01504593 Registered office: The Lawn, 22-30 Old Bath Road Newbury, Berkshire, RG14 1QN, UK
