> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] Behalf Of Andy Polyakov
> Sent: Saturday, January 29, 2005 9:23 AM
> To: openssl-dev@openssl.org
> Subject: Re: Openssl-SNAP-20050129 Re: Openssl-SNAP-20050125 Re:
> Openssl-SNAP-20050124
&g
On Sat, Jan 29, 2005 at 06:23:29PM +0100, Andy Polyakov wrote:
> >... ./sha512t
> >
> >Illegal instruction
> >
> >*** Error code 132
>
> This means that your kernel does not support SSE2 and you have to other
> choice but to configure with no-sse2 and give up SSE2 enhancements. I'm
> sorry if I'
... ./sha512t
Illegal instruction
*** Error code 132
This means that your kernel does not support SSE2 and you have to other
choice but to configure with no-sse2 and give up SSE2 enhancements. I'm
sorry if I've lead you to wrong expectations, but my BSD experience was
not broad enough to foresee
On Tue, Jan 25, 2005 at 11:40:41PM +0100, Andy Polyakov wrote:
> >../libcrypto.so: undefined reference to `dlerror'
> >../libcrypto.so: undefined reference to `dlclose'
> >../libcrypto.so: undefined reference to `dlopen'
> >../libcrypto.so: undefined reference to `dlsym'
> >../libcrypto.so: undefin
../libcrypto.so: undefined reference to `dlerror'
../libcrypto.so: undefined reference to `dlclose'
../libcrypto.so: undefined reference to `dlopen'
../libcrypto.so: undefined reference to `dlsym'
../libcrypto.so: undefined reference to `AES_encrypt'
../libcrypto.so: undefined reference to `AES_Td'
