My development enviroment is Solaris 2.7/i86pc, with gcc 2.8.1, and
native as/ld. When compiling openssl-SNAP=19990304, I get errors:
root@telgar:openssl-SNAP-19990304/crypto/ripemd 123# make
(cd ../..; make -f Makefile.ssl DIRS=crypto SDIRS=ripemd sub_all)
make[1]: Entering directory
`/home/spierce/Src/Crypto/openssl-SNAP-19990304'
making crypto...
make[2]: Entering directory
`/home/spierce/Src/Crypto/openssl-SNAP-19990304/crypto'
making all in ripemd...
make[3]: Entering directory
`/home/spierce/Src/Crypto/openssl-SNAP-19990304/crypto/ripemd'
gcc -E -DSOL asm/rm86unix.cpp | sed 's/^#.*//' > asm/rm86-sol.s
as -o asm/rm86-sol.o asm/rm86-sol.s
Assembler: rmd-586.s
aline 664 : syntax error
aline 677 : syntax error
...
aline 1404 : syntax error
aline 1417 : syntax error
Too many errors - Goodbye
make[3]: *** [asm/rm86-sol.o] Error 127
make[3]: Leaving directory
`/home/spierce/Src/Crypto/openssl-SNAP-19990304/crypto/ripemd'
make[2]: *** [subdirs] Error 1
make[2]: Leaving directory
`/home/spierce/Src/Crypto/openssl-SNAP-19990304/crypto'
make[1]: *** [sub_all] Error 1
make[1]: Leaving directory
`/home/spierce/Src/Crypto/openssl-SNAP-19990304'
make: *** [top] Error 2
The assembler (Solaris 2.7/i86pc stock) is not understanding 'leal'.
I've reported this to Sun as a bug, I expect a responce on Monday if
they think it's a bug or a feature. <-:
I'm planning on testing on Solaris 2.6 too, but my Solaris 2.6 disk
is dead, and so I need to get a new one from Sun.
There are three solutions for this problem:
o fix as (Sun ticket #3835693)
o replace as (done and tested)
o not use the Intel assembler versions for Solaris/x86 2.7 (done,
but untested)
Until 'as' is fixed, I compiled gas from the current binutils on
ftp.gnu.org. I created an installable package containing only gas, and
modified the Makefiles and Configure script to use 'gas' instead of 'as'
for solaris-gcc-x86.
The changes to replace 'as' with 'gas' are small, but there are a lot
of them scattered throughout several Makefiles and the Configure script.
I have a patch, but I don't know the rules or procedure to submit the
patch, or if I even should.
How should I proceed?
Steve
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
