If you're running it on a processor with SSE, and it's failing, what does this tell you? SSE2 is required to use the asm code path. SSE just doesn't cut it.
In the fips-1.2 configuration step, use ./config fipscanisterbuild no-asm -Kyle H On Fri, Jan 9, 2009 at 9:25 AM, PGNet <pgnet.trash+...@gmail.com> wrote: > Hi Stephen, > > On Fri, Jan 9, 2009 at 8:18 AM, Dr. Stephen Henson <st...@openssl.org> wrote: >> You can get the answer with "openssl errstr" or by checking the source file >> referenced. > > Noted. Thanks. > >> So either use a box supporting SSE2 or use a pure C build (no-asm) which >> will have poorer performance. > > I have no problem with poorer performance -- on this box, anyway. > > But just to be certain, is SSE*2* required, rather than 'just' SSE? > > My box, > > cat /proc/cpuinfo | grep flags > flags : fpu vme de pse tsc msr pae mce cx8 sep mtrr pge mca cmov pat > pse36 mmx fxsr sse up > > Thanks. > ______________________________________________________________________ > 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
