Hi Andy, > I assume ABEND.LOG is answer to this question... yup. > But you still have to confirm that the fault is actually triggered by > metrowerks assembler module. see my other post I just sent.
> On related note question is what prevents you from always using nasm? Or > rather do we actually need to support for metrowerks assembler? > Basically if there is one working configuration for netware, what do we > need second one for? well, that wasnt my idea, but it was 'historically'. I guess The Novell folks who did the initial OpenSSL port just started with the Metrowerks Assembler since its part of the Compiler package, and developers got this package delivered; probably also for debugging reasons since Metrowerks CodeWarrior comes with an IDE with source-level debugger; though at the moment I dont have that IDE installed, but use commandline tools only which is far more flexible reagrding path settings etc. > Bottom line. I'd rather consider omitting metrowerks assembler support. A. probably if there's no way to work around the issue; but currently it seems that only 2 out of the 13 asm files are affected - that are ripemd and aes (the rc4 fix I recently posted seems to work - and the aes code wasnt used at all up to now). BTW. can you tell me for what the CPUID asm code is good for? Well, I can imagine what it does, but I'm curious for what its used.... thanks for your replies! Guenter. ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List openssl-dev@openssl.org Automated List Manager [EMAIL PROTECTED]
