Jeff Fulmer wrote:
I'm trying to compile openssl-0.9.8a on HPUX with the following
configuration:
#!/bin/sh
./config \
--prefix=/usr/local/ssl \
no-asm \
threads \
zlib \
-fPIC
It barfs here everytime. I wouldn't think it would go to the assembler
with the no-asm:
gcc -I.. -I../.. -I../../include -DZLIB -DOPENSSL_THREADS -DDSO_DL
-fPIC -D_REENTRANT -march=2.0 -O3 -DB_ENDIAN -D_REENTRANT -c -o
b_print.o b_print.c
/var/tmp/cc8MBUWc.s: Assembler messages:
/var/tmp/cc8MBUWc.s:1242: Error: Unknown opcode: `fneg'
make[2]: *** [b_print.o] Error 1
make[2]: Leaving directory
`/home/jdfulmer/src/openssl-0.9.8a/crypto/bio'
make[1]: *** [subdirs] Error 1
make[1]: Leaving directory `/home/jdfulmer/src/openssl-0.9.8a/crypto'
make: *** [build_crypto] Error 1
Any thoughts?
First thought, _which_ HPUX revision and platform (PA or IPF)? (I'm guessing PA
since it says -march=2.0 but who knows... :)
Second, _which_ gcc version?
Third, is the /var/tmp/cc8MBUWc.s file an assembly file from openssl, or is it
perhaps an assembly file from the compiler and there is a mismatch bewteen the
front-end and the back-end? Is gcc using the gnu (?) assembler or the HP
assembler? I've no idea which it should use, but do recall there being issues
in that area in the past in other places.
Fourth - any particular reason you are tossing-out any of the previous good work
done for fast assembly versions of some things?
rick jones
BTW, that reminds me of something I've been meaning to ask - does the --no-asm
simply preclude using stuff in a -s file, or will it also disable the use of
assembly that is inline in a .c file? I seem to recall that some of the
hand-crafted assembly routines for some platforms are in .c files rather than .s
files.
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List openssl-users@openssl.org
Automated List Manager [EMAIL PROTECTED]
