[openssl.org #922]

2004-07-21 Thread via RT
tesss __ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]

Porting OpenSSL

2004-07-21 Thread Gary Walters
I have been working on porting OpenSSL to the THEOS Operating System. The C compiler is ANSI C compliant and "mostly" ISO C99 compliant. However, it is not as feature rich as GCC. . My main problem is with the function pointer callbacks that accept parameters. I'm finding that I have to

Re: Porting OpenSSL

2004-07-21 Thread Richard Levitte - VMS Whacker
In message [EMAIL PROTECTED] on Wed, 21 Jul 2004 15:00:15 -0600, Gary Walters [EMAIL PROTECTED] said: garwal I have been working on porting OpenSSL to the THEOS Operating garwal System. The C compiler is ANSI C compliant and mostly ISO garwal C99 compliant. However, it is not as feature rich

Re: Porting OpenSSL

2004-07-21 Thread Stephen Sprunk
Thus spake Gary Walters [EMAIL PROTECTED] I have been working on porting OpenSSL to the THEOS Operating System. The C compiler is ANSI C compliant and mostly ISO C99 compliant. However, it is not as feature rich as GCC. . My main problem is with the function pointer callbacks that accept

Re: Porting OpenSSL

2004-07-21 Thread J Harper
Gary, MatrixSSL might be a good alternative, it's designed to be easily portable and I believe only uses callbacks with parameters in one spot (for X.509 certificate validation). Var args are also not used in any of the APIs, which may help if your compiler is less than ANSI compliant.. The