Replies below.  But the meta-question is "does there exist
step by step instructions for compiling the openssl FIPS module.

It seems odd that this is supposed to be so strict, yet the process seems 
to be
to google around and try various options until something works.

> From: "Dr. Stephen Henson" <st...@openssl.org>
> To: openssl-users@openssl.org
> Date: 09/09/2011 09:45 AM
> Subject: Re: out range error compiling fips 1.2.3
> Sent by: owner-openssl-us...@openssl.org
> 
> On Thu, Sep 08, 2011, Kenneth Goldman wrote:
> 
> > I'm getting this error compiling openssl-fips-1.2.3.tar.gz, which 
seems to 
> > be the latest.  It seems to be well known on openssl-dev, but I don't 
know 
> > what to do about it.  Any ideas?
> > 
> > gcc -I.. -I../.. -I../../include -DOPENSSL_THREADS -D_REENTRANT 
> > -DDSO_DLFCN -DHAVE_DLFCN_H -m64 -DL_ENDIAN -DTERMIO -O3 -Wall 
> > -DMD32_REG_T=int -DOPENSSL_BN_ASM_MONT -DSHA1_ASM -DSHA256_ASM 
> > -DSHA512_ASM -DMD5_ASM -DAES_ASM -c  -o md5-x86_64.o md5-x86_64.s
> > md5-x86_64.s: Assembler messages:
> > md5-x86_64.s:41: Error: 0xd76aa478 out range of signed 32bit 
displacement
> > 
> > > uname -a
> > Linux cainl.watson.ibm.com 2.6.32-131.6.1.el6.x86_64 #1 SMP Mon Jun 20 

> > 14:15:38 EDT 2011 x86_64 x86_64 x86_64 GNU/Linux
> > 
> 
> If you can get OpenSSL to compile despite that error (e.g. different 
version
> of the assembler) it wont matter because that file isn't used in the 
FIPS
> module itself. It's just a side effect of the 1.2 build process that it 
needs
> to build a complete vesion of OpenSSL as well as the module.

I thought I was not allowed to touch any of the build configuration.

This is a standard Linux RHEL 6.1 with standard gnu tools.

> 
> > ~~~~~~~~~~~~~~
> > 
> > A second question.  In researching this error, I saw someone compile 
with 
> > 
> >         > ./config fipscanisterbuild
> > 
> > That's not in the INSTALL file.  Do I need this?
> > 
> 
> That is for testing purposes for the unvalidated 2.0 module only. The 
1.2
> module uses
> 
> ./config fipscanister
> 
> instead.

I tried that and got:

> ./config fipscanister 
Operating system: x86_64-whatever-linux2
Configuring for linux-x86_64
target already defined - linux-x86_64 (offending arg: fipscanister)

Reply via email to