[openssl.org #464] TSU NOTIFICATION - encryption

2003-01-19 Thread Andy Polyakov via RT
All discussed issies are adressed. Ticket is being resolved. A. __ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager

Re: [openssl.org #464] TSU NOTIFICATION - encryption

2003-01-18 Thread Andy Polyakov via RT
Config was adding 386 to the Configure line causing the build to fail on the assembler modules. in what way? UX:as: ERROR: asm/sx86-elf.s:35:invalid register for instruction: %al in xchg Would it work if you add b to xchg mnemonic, i.e. make it look xchgb

Re: [openssl.org #464] TSU NOTIFICATION - encryption

2003-01-18 Thread Andy Polyakov via RT
Have the 5 section look something like -- 5) if [ `echo x$VERSION | sed -e 's/\..*//'` = x7 ]; then echo i586-sco-unixware7; exit 0 elif [ `echo x$VERSION | sed -e 's/\..*//'` = x8 ]; then echo

Re: [openssl.org #464] TSU NOTIFICATION - encryption

2003-01-18 Thread Tim Rice
On Sat, 18 Jan 2003, Andy Polyakov via RT wrote: Config was adding 386 to the Configure line causing the build to fail on the assembler modules. in what way? UX:as: ERROR: asm/sx86-elf.s:35:invalid register for instruction: %al in xchg Would it work

Re: [openssl.org #464] TSU NOTIFICATION - encryption

2003-01-18 Thread Tim Rice via RT
On Sat, 18 Jan 2003, Andy Polyakov via RT wrote: Config was adding 386 to the Configure line causing the build to fail on the assembler modules. in what way? UX:as: ERROR: asm/sx86-elf.s:35:invalid register for instruction: %al in xchg Would it work

Re: [openssl.org #464] TSU NOTIFICATION - encryption

2003-01-18 Thread Andy Polyakov
To summarize. I'm hardcoding i586 to all Caldera/SCO targets. And according to RT#460 we also should get rid of -lresolv on those platforms, right? A. And yes, get rid of -lresolv on the sco5 (OpenServer 5) targets. The question also is if it's needed even in unixware-2.* lines. As

Re: [openssl.org #464] TSU NOTIFICATION - encryption

2003-01-18 Thread Tim Rice
On Sat, 18 Jan 2003, Andy Polyakov via RT wrote: Have the 5 section look something like -- [snip] Updated config is in both HEAD and 0.9.7-stable CVS. Please verify and reply so that the ticket can be resolved. A. UX:sh (./config): ERROR: ./config: Syntax error at line 442: `fi'

Re: [openssl.org #464] TSU NOTIFICATION - encryption

2003-01-17 Thread Tim Rice
On Fri, 17 Jan 2003, Andy Polyakov via RT wrote: NOTIFICATION: The attached patch applies to openssl-0.9.7. Does it really have to be so complicated? I mean all you have to do is Perhaps not. I just pulld some code from the FreeBSD section. to tell i386 and none-i386 apart, right?

Re: [openssl.org #464] TSU NOTIFICATION - encryption

2003-01-17 Thread Andy Polyakov via RT
Config was adding 386 to the Configure line causing the build to fail on the assembler modules. in what way? Not really. So you mean that it's not like it fails, but generates not optimal code. Minimum processor on any current UnixWare is a pentium. The older

Re: [openssl.org #464] TSU NOTIFICATION - encryption

2003-01-17 Thread Tim Rice
On Fri, 17 Jan 2003, Andy Polyakov via RT wrote: Config was adding 386 to the Configure line causing the build to fail on the assembler modules. in what way? Not really. So you mean that it's not like it fails, but generates not optimal code. No, it fails.

Re: [openssl.org #464] TSU NOTIFICATION - encryption

2003-01-17 Thread Tim Rice via RT
On Fri, 17 Jan 2003, Andy Polyakov via RT wrote: Config was adding 386 to the Configure line causing the build to fail on the assembler modules. in what way? Not really. So you mean that it's not like it fails, but generates not optimal code. No, it