We can give an access to our system. How can we contact a developer? -----Original Message----- From: owner-openssl-us...@openssl.org [mailto:owner-openssl-us...@openssl.org] On Behalf Of Dr. David Kirkby Sent: April 23, 2010 3:13 PM To: openssl-users@openssl.org Subject: Re: building OpenSSL 0.9.8/1.0.0 on Solarisx86
Alona Rossen wrote: > Specifyng solaris64-x86_64-gcc as a target results in a 64-bit library, > while we need a 32-bit library. Oh, sorry i missed that. I also failed to create a 32-bit library. It so happened that in the software I wanted to develop, 64-bit was more sensible, so I ignored the fact I was unable to create a 32-bit library. I believe you are correct in saying this will not work. You will probably need the assistance of a developer in that case. It might be easier if you can give them access to a Solaris system, though with VirtualBox, they should be able to set one up easily. dave > > -----Original Message----- > From: owner-openssl-us...@openssl.org > [mailto:owner-openssl-us...@openssl.org] On Behalf Of Dr. David Kirkby > Sent: April 23, 2010 1:33 PM > To: openssl-users@openssl.org > Subject: Re: building OpenSSL 0.9.8/1.0.0 on Solarisx86 > > Alona Rossen wrote: >> >> >> Hello, >> >> >> >> I built 32-bit OpenSSL 0.9.8 and OpenSSL 1.0.0 on Solaris10x86_64 >> (64-bit kernel on Intel) with gcc compiler. Makefiles were generated >> with the following command: >> >> >> >> "Configure solaris-x86-gcc" > > Try solaris64-x86_64-gcc as the target, which was the default when I run > Configure. > > I've built 0.9.8l on a Sun Ultra 27 (quad core 3.33 GHz Xeon processor) > using > OpenSolaris 06/2009 and gcc 4.3.4. It builds fine and passes tests > > DONE via BIO pair: TLSv1, cipher TLSv1/SSLv3 DHE-RSA-AES256-SHA, 1024 > bit RSA > DONE via BIO pair: TLSv1, cipher TLSv1/SSLv3 DHE-RSA-AES256-SHA, 1024 > bit RSA > DONE via BIO pair: TLSv1, cipher TLSv1/SSLv3 DHE-RSA-AES256-SHA, 1024 > bit RSA > 10 handshakes of 256 bytes done > Approximate total server time: 0.05 s > Approximate total client time: 0.00 s > Test IGE mode > ../util/shlib_wrap.sh ./igetest > Test JPAKE > ../util/shlib_wrap.sh ./jpaketest > No JPAKE support > make[1]: Leaving directory `/export/home/drkirkby/openssl-0.9.8l/test' > util/opensslwrap.sh version -a > OpenSSL 0.9.8l 5 Nov 2009 > built on: Fri Apr 23 18:24:58 BST 2010 > platform: solaris64-x86_64-gcc > options: bn(64,64) md2(int) rc4(1x,char) des(idx,cisc,16,int) idea(int) > > blowfish(ptr2) > compiler: gcc -DOPENSSL_THREADS -D_REENTRANT -DDSO_DLFCN -DHAVE_DLFCN_H > -m64 -O3 > -Wall -DL_ENDIAN -DMD32_REG_T=int -DOPENSSL_BN_ASM_MONT -DSHA1_ASM > -DSHA256_ASM > -DSHA512_ASM -DMD5_ASM -DAES_ASM > OPENSSLDIR: "/usr/local/ssl" > drkir...@hawk:~/openssl-0.9.8l$ > > > I have not tried this on Solaris 10 though - at least not on x86. I have > built > versions on SPARC before, but that is less relevant to you. > > dave > ______________________________________________________________________ > OpenSSL Project http://www.openssl.org > User Support Mailing List openssl-users@openssl.org > Automated List Manager majord...@openssl.org > ______________________________________________________________________ > OpenSSL Project http://www.openssl.org > User Support Mailing List openssl-users@openssl.org > Automated List Manager majord...@openssl.org > ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List openssl-users@openssl.org Automated List Manager majord...@openssl.org ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List openssl-users@openssl.org Automated List Manager majord...@openssl.org
