Hello Andy, thanks for your help.
> > Clues? Google for 3c48692aceb44f85cf99c985154c15b79e6baef0, which is > your own hash value... gcc-bugs report from 2000 maintains that gcc 2.96 > fails in exactly same way on PowerPC, but not 2.95.3... Does it sound > like problem with test program? No, it sound like compiler bug... indeed, I read that post too but found no further evidence or replies. However I found no ppc asm to disable... so I started playing with optimization flags. Using only -O1 works -O1 and frame_pointer works too (besides, according to gcc manual, -O2 should automatically set to omit framepoitner where appropriate). -O2 fails. I tried then adding some options to -O1 and I ended up discovering a new error (after the sha test passed). So I really think gcc 2.96 is having problems. It is intersting how only OpenSSL triggers problems, it probably stresses the compiler optimizations more. I reverted to gcc 2.95.3 and indeed openssl 0.9.6m compiled fine with out-of-the-box options and apssed all tests. SO I guess MkLinux will revert to 2.95 for the R2 release and jump to gcc3 in the upcoming R3. > > You could as well just stick to instructions in ./README to get rid of > assembler and examine line in ./Configure to spot -DL_ENDIAN and realize > it's not appropriate in your case. You didn't actually have to modify > the source code. A. it is using B_ENDIAN which is correct. -R ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List openssl-dev@openssl.org Automated List Manager [EMAIL PROTECTED]
