> I have a problem installing the openSSL on my SGI IRIX6.2:
> The gcc compiler doesnt understand "mapi=n32". As I�m only little
> familiar with compiling stuff, would someone please tell me what mapi
> stands for?
It's "abi," not "api," and it stands for Application Binary Interface,
or in other words subroutine calling convention. IRIX 6 supports three
distinct ABIs commonly dubbed as o32 (IRIX 5 legacy ILP32 ABI), n32
(IRIX 6 ILP32 ABI, to the difference from o32 64-bit arguments are
permitted and more important 64-bit register contents aew preserved by
OS kernel during context switches) and n64 (IRIX 6 LP64 ABI).
> OpenSSL self-test report:
> OpenSSL version: 0.9.6a
> Last change: Fix a couple of memory leaks in PKCS7_dataDecode()...
> Options: -mips3
> OS (uname): IRIX MZINDI1 6.2 06101030 IP22
> OS (config): mips3-sgi-irix
> Target (default): irix-mips3-gcc
> Target: irix-mips3-gcc
> Compiler: gcc version 2.7.2
I can't tell for sure, but your compiler is very likely capable of
generating o32 code only. Now if you ought to use this compiler, then
the only option you have is to manually configure the toolkit with
'./Configure irix-gcc' instead of relying on './config'. If you're free
to use another compiler and/or care about performance, then I would
recommend to upgrade to 2.95 (or whatever they have at
http://freeware.sgi.com/). As for the performance issue. Note that it's
not like gcc 2.95 generates so much better code. The issue is actually
ABI. As I already mentioned n32 permits 64-bit registers which in turn
makes it possible to reduce amount of multiplication needed to perform
the public-key operations. And on top of that OpenSSL offers an assemler
support (i.e. for n32 and n64, but not for o32 ABIs) turbocharging the
public-key oprtations by factor of 3.
Andy.
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
