George -
I built using the same tools - gmake, icc, etc. I used the "standard" perl, the one that came with the iSeries Tools for Developers, and did not recompile it. All the source and perl files were marked CCSID 437, and everything was built for CCSID 37.
My source modifications included ASCII/EBCDIC translation tables from the QTCPASC and QTCPEBC tables in QUSRSYS. All the tests run (via "make test") and pass (I did need to make a few changes). I also convert all the test .cnf and .pem files to CCSID 37 to get the tests to pass.
The actual calling application I'm using is built for CCSID 850; it just converts parameter data where necessary when making openssl calls. Could you do the same from your CCSID 500 application? I think it's only necessary when specifying filenames and such.
BTW, I'm unable to run the "openssl speed" program - the process quits when it gets a SIGALRM. Did you get this working?
Thanks
Brian
-----Original Message-----
From: George Shaw [mailto:[EMAIL PROTECTED]
Sent: 22 August 2003 17:25
To: '[EMAIL PROTECTED]'
Subject: Re: as/400 port?
Hi Brian,
I started work on an AS/400 port last year, but was unable to complete the
task. I had OpenSSL compiled (that was the easy part) and running some
manual tests, but had been unable to get the test environment working. The
reason for this is that my project needed to build OpenSSL to run under
CCSID 500, and I was not able at the time to get Perl built for CCSID 500.
Then I was diverted onto other priorities (yes, for over a year).
As it happens, by coincidence, I now have some customers who need OpenSSL on
the AS/400, and I was just browsing the mailing lists to look at the current
status when I saw your latest contribution.
So a few quick questions.
1. How does your port of OpenSSL to the AS/400 handle CCSIDs?
2. What build environment are you using? I used the IBM-supplied GNU
utilities, which includes gmake, gawk and icc (cc/gcc emulator), re-built
for use with CCSID 500, which means that I can use the standard OpenSSL
build method.
3. Did you get the OpenSSL test environment working, i.e. using Perl? If
so, was this a standard Perl, or a re-built Perl for a different CCSID?
If your work has not covered other CCSIDs, then I'd be happy to contribute
some work to make a CCSID 500 port, and possibly work towards getting
OpenSSL working on other CCSIDs.
G.
---------------------------
George Shaw
Senior Software Engineer
Axway
a Sopra Group company
Tel: +44 (0) 7802 452186
Fax: +44 (0) 1454 299684
email: [EMAIL PROTECTED]
www.axway.com
---------------------------
Ce message est exclusivement destin� aux personnes dont le nom figure
ci-dessus. Il peut contenir des informations confidentielles dont la
divulgation est � ce titre rigoureusement interdite. Dans l'hypoth�se o�
vous avez re�u ce message par erreur, merci de le renvoyer � l'adresse
e-mail ci-dessus et de d�truire toute copie.
This message may contain confidential and proprietary material for the sole
use of the intended recipient. Any review or distribution by others is
strictly prohibited. If you are not the intended recipient, please contact
the sender and delete all copies.
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Brian C Morris
Sent: 21 August 2003 12:57
To: [EMAIL PROTECTED]
Subject: Re: as/400 port?
I'm wrapping up my iSeries port and am wondering how best to submit it?
I've modified the 0.9.7b source - would diffs against this be easiest to
integrate?
Thanks
Brian
