netd> > One thing you could try (and this is written in the docs) is
netd> > configuring OpenSSL with "no-asm" and see if that makes a different.
netd> >
netd> 
netd> THAT WORKED!!! Thanks I only hope that 'no-asm'  did not affect the
netd> integrity of the build though. How do we know?

All it does is to avoid using the special assembler implementations of
some core routines.  The basic C implementation is then used instead.
The assembler routines are supposed to be more optimal, but it's known
that it doesn't always work.  That's why the no-asm optoin is there.
However, we did expect to get errors directly from the assembler
rather than from the linker later on...

netd> > Then there's one thing I fail to understand:
netd> >
netd> > netd> fw:/usr/src/openssl-0.9.4 # make
netd> > netd> -I/usr/src/openssl-0.9.4/include/openssl
netd> >
netd> > What does that -I thingy do there?
netd> 
netd> They said I could do that in the docs, I = inlcude

In the "* COMPILING existing applications", I assume.  That doesn't
have anything to do with building OpenSSL itself, it's about how other
applications that use OpenSSL should be built.

-- 
Richard Levitte   \ Spannv�gen 38, II \ [EMAIL PROTECTED]
Chairman@Stacken   \ S-168 35  BROMMA  \ T: +46-8-26 52 47
Redakteur@Stacken   \      SWEDEN       \ or +46-708-26 53 44
Procurator Odiosus Ex Infernis             -- [EMAIL PROTECTED]
           Member of the OpenSSL development team

Unsolicited commercial email is subject to an archival fee of $400.
See <http://www.stacken.kth.se/~levitte/mail/> for more info.
______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
Development Mailing List                       [EMAIL PROTECTED]
Automated List Manager                           [EMAIL PROTECTED]

Reply via email to