If you are going to be supporint OS/2, I recommend that you start by
incorporating the OS/2 patches that Dirk Ohme wrote for the IBM
compiler.  I've been using them on OS/2 for some time now and would be
interested in working with you on the OS/2 support. 



> Hi,
> 
> I am in the process of porting the OpenSSL libs to compile using the Watcom C/C++ 
>compiler and the WASM assembler. I will be supporting OS/2 & Win32 perhaps 32-bit DOS 
>if there is demand for it. I will also be producing a version of OpenSSL that will 
>compile on OS/2 using the EMX+GCC environment. I would like to see this incorporated 
>into the OpenSSL distribution.
> 
> What is the best way to incorporate code changes? For C source code changes I can 
>make use of the following predefined macros:
> 
> __EMX__         EMX Specific Changes
> __WatcomC__     Watcom Specific Changes
> __OS2__         OS/2 Specific Changes
> 
> 
> The Win32 ASM code seems to work for the most part. Watcoms WASM uses a slightly 
>different calling convention though. This can be addressed but require the ASM 
>function prototypes to add cdecl:
> 
> extern int myfuntion(void);
> 
> would be:
> 
> extern int cdecl myfunction(void);
> 
> I also noticed that the WASM does not like part of the SHA1-586.ASM code. It seems 
>that sha1_block_asm_host_order code is inside of the sha1_block_asm_data_order code. 
>By moving this code outside of the data_order code the ASM code compiles fine.
> 
> Should I just add the cdecl to the prototypes (wraped in #ifdefined __WatcomC__) or 
>should the perl code be modified (this would require help from someone with better 
>perl & asm experience)?
> 
> 
> Also some advice would be appreciated on how to handle eliminating the use of the 
>Configure scripts and shell scripts as these are not appropriate for this environment.
> 
> Is there a list of the various compile time flags used for building the OpenSSL libs?
> 
> What *.h files are autogenerated?
> 
> Is there a list showing the dependencies between the various modules?
> 
> tks,
> 
> PS: What was the reason for moving all the sha1 code from the *.c file into the *.h 
>file?
> 
> -- 
> ---------------------------------------------------------------
> William H. Geiger III      http://www.openpgp.net  
> Geiger Consulting    
> 
> Data Security & Cryptology Consulting
> Programming, Networking, Analysis
>  
> PGP for OS/2:               http://www.openpgp.net/pgp.html
> E-Secure:                   http://www.openpgp.net/esecure.html
> ---------------------------------------------------------------
> 
> ______________________________________________________________________
> OpenSSL Project                                 http://www.openssl.org
> Development Mailing List                       [EMAIL PROTECTED]
> Automated List Manager                           [EMAIL PROTECTED]
> 



                  Jeffrey Altman * Sr.Software Designer
                 The Kermit Project * Columbia University
               612 West 115th St * New York, NY * 10025 * USA
     http://www.kermit-project.org/ * [EMAIL PROTECTED]


______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
Development Mailing List                       [EMAIL PROTECTED]
Automated List Manager                           [EMAIL PROTECTED]

Reply via email to