I hate buggy compilers! Building crypto/rand/rand_lib.c with "-g" flag fixes the randtest problem and allows most of the tests to succeed. The treq fails because openssl can't find "subjectKeyIdentifier". Rebuilding crypto/x509v3 with "-g" clears this up. What a pain. (At this point the obvious thing to do is just build all of OpenSSL with "-g" but the resulting objects with embedded debug symbols are huge, 10x size at least.)
-- Howard Chu Chief Architect, Symas Corp. Director, Highland Sun http://www.symas.com http://highlandsun.com/hyc Symas: Premier OpenSource Development and Support > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of Howard Chu > Sent: Thursday, August 22, 2002 3:30 PM > To: [EMAIL PROTECTED] > Subject: RE: [openssl.org #243] OpenSSL 0.9.6g fail on IBM OS/390 > > > Removing "-O" from CFLAGS and recompiling the crypto/des directory > fixed the > mdc2test error. Getting past this, randtest fails. Rebuilding without > optimization hasn't affected that problem. (How ironic, the optimizer gives > us random results when we don't want them, and the random number > lib doesn't > give random results, tho we do want them...) > > do29:~/openssl-0.9.6g/test> ./randtest > test 1 failed, X=2694 > test 1 done > test 2 failed, X=31739.44 > test 2 done > test 3 failed, bit=0 run=1 num=413 > test 3 failed, bit=0 run=2 num=213 > test 3 failed, bit=0 run=3 num=199 > test 3 failed, bit=0 run=4 num=153 > test 3 failed, bit=0 run=5 num=67 > test 3 failed, bit=0 run=6 num=711 > test 3 failed, bit=1 run=1 num=1248 > test 3 failed, bit=1 run=2 num=280 > test 3 failed, bit=1 run=3 num=136 > test 3 failed, bit=1 run=4 num=59 > test 3 failed, bit=1 run=5 num=11 > test 3 failed, bit=1 run=6 num=22 > test 3 done > test 4 failed, bit=0 run=34 num=54 > test 4 done > > -- Howard Chu > Chief Architect, Symas Corp. Director, Highland Sun > http://www.symas.com http://highlandsun.com/hyc > Symas: Premier OpenSource Development and Support > > > -----Original Message----- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED]]On Behalf Of Howard Chu via RT > > > mdc2test produces different results every time it is executed. Seems like > > something is uninitialized and filling with random data on every > > invocation. > > Does this sound familiar to anyone? All the tests up to this point are > > correct, many of the tests after this point fail. It seems odd > to me since > > mdc2 uses DES and the destest succeeds. > > > ______________________________________________________________________ > OpenSSL Project http://www.openssl.org > Development Mailing List [EMAIL PROTECTED] > Automated List Manager [EMAIL PROTECTED] > ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
