> when using the 64-bit gcc compiler...i get the following on the 'make test'...  any 
> suggestions?

Be more specific. Less we have to guess, better answers you get and 
faster. Should we start testing all known 64-bit gcc compilers? Note 
that README explicitly mentions that you're expected to submit 'make 
report' output.

> somebody else posted this question a while back, but i do not see a reply.

Also note that README suggests a number of steps prior submitting the 
bug report, most notably reducing optimization level in order to exclude 
compiler bugs, which we can't possibly be responsible for.

But in either case...

> ... if [ "solaris64-sparcv9-gcc" = "Cygwin" ]; ... ./rmdtest

Aha! SPARC Solaris...

> error calculating RIPEMD160 on ''
> got c12836ad0d061da6ccde02fb0b5be87f0c62a4a5 instead of 
> 9c1185a5c5e9fc54612808977ee8f548b2258d31

If it's gcc 3.x, then I bet on compiler bug. Lower optimization level 
and see if test passes. Configuring with -DMD32_REG_T=int might do the 
trick as well... A.

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

Reply via email to