OK, one step forward. I guess that previously you had a path error because you need to create a link (correctly) to point to your gmake program.
And the CCSID of the delivered tools package is unimportant - it's the CCCSID of the unpacked programs that is important. Hmmm. Message ID . . . . . . . . . : MCH3601 Message file . . . . . . . . : QCPFMSG Library . . . . . . . . . : QSYS Message text . . . . . . . . : Pointer not set for location referenced. So the delivered icc is not as robust as it should be ... As I said before, I had to re-compile mine for CCSID 500, so had the source, so I was able to easily track down problems such as this. I'm looking at my source, and the only changes that I made to icc look relatively trivial - but these are changes from 9 years ago, so my memory may not be 100% accurate. And I suspect that the testing that I've done has been using my version of icc - while it executes as CCSID 500, it can be used to make binaries of any CCSID. You have a couple of options, I think. The techie option is to get the source for icc and find and fix the pointer error. Icc is just a wrapper program that translates compile requests from a UNIX-like string to the correct OS/400 command (as you can see from the output). So it is easy to debug. The more difficult option is to try to determine which argument is upsetting icc empirically, and then work around that - it does work out of the box, but as you can see, is a little temperamental. Unfortunately, I don't think that IBM offer support for the GNU utilities - I don't know if they still offer the source code. If you prefer the techie option, and they don't, then I can probably send you the source package (at your own risk). BTW. I'm not sure what your requirements are, but OpenSSL will run on the AS/400 as AIX binaries under the PASE environment. Which could be a simpler option. Good luck. G. ________________________________ From: owner-openssl-us...@openssl.org [mailto:owner-openssl-us...@openssl.org] On Behalf Of Pankaj Aggarwal Sent: 05 April 2010 14:51 To: openssl-users@openssl.org Subject: Re: OpenSSL on IBMi Got it working ! Stuck in another error in openssl/crypto :-( icc -I. -I.. -I../include -DOPENSSL_THREADS -D_MULTI_THREADED -v -O4 -DB_ENDI AN -DCHARSET_EBCDIC -DNO_SYS_PARAM_H -D_ALL_SOURCE -DNO_SYSLOG -qTGTRLS=*CURR ENT -qTGTCCSID=37 -c cryptlib.c -o cryptlib.o command = CRTCMOD MODULE(CRYPTO/CRYPTLIB) SRCSTMF('cryptlib.c') DEFINE('OPENS SL_THREADS' '_MULTI_THREADED' 'B_ENDIAN' 'CHARSET_EBCDIC' 'NO_SYS_PARAM_H' '_ ALL_SOURCE' 'NO_SYSLOG' ) OPTIMIZE(40) TEXT('/home/qsecofr/openssl-0.9.8e/crypto/cryptlib.o') SYSIFCOPT(*IFSIO) TGTRLS(*CURRENT) TGTCCSID(37) OPTION(*LOG> iMSG ) AQAPTL/ICC: Unexpected exception MCH3601 On Mon, Apr 5, 2010 at 4:06 PM, Pankaj Aggarwal <pankaj.aggar...@gmail.com> wrote: > Hi Shaw,Q > > I do have the qsh porting tools installed (which include icc, gmake > etc.). I checked the CCSID for these tools. it's 1200. > Now since my openssl files have been extracted from tar in qsh > environment, they have the CCSID of 37. Should I get the IBM tools for > CCSID 37? > > I tried to set the QIBM_CSSID variable in qsh environment to 1200, but > the extracted openssl files still have CCSID of 37. > > Pankaj > > > On Sun, Apr 4, 2010 at 8:23 PM, Shaw Graham George <gs...@axway.com> wrote: >> >> You should read the detail of the readme files for this and maybe previous ports at rt.openssl.org. >> >> Firstly, for this port to work, you need to install the IBM AS/400 GNU utilities - it doesn't look like you have. I'm not sure of their current status, but at the time these were unsupported utilities only obtainable from IBM. They are delivered as CCSID 37 binaries, so you need to know what CCSID you wish to support. I had to get the source from IBM (by special request) and re-compile gmake to run as CCSID 500. >> >> AFAIK (but I am a little out of date), any gmake delivered with the AS/400 is a PASE binary. >> >> Regarding perl, I can't remember if perl (for CCSID 37) from CPAN worked. I certainly failed to port CPAN perl to CCSID 500 (and ran out of time to investigate further). But this made no difference to me as I was building OpenSSL for about 13 platforms, so I could run the configure option (that uses perl) on UNIX. >> >> If was looking again now, and looking for AS/400-independence, I'd investigate if I could run a PASE version of perl for the configure. >> >> G. >> >> >> -----Original Message----- >> From: owner-openssl-us...@openssl.org [mailto:owner-openssl-us...@openssl.org] On Behalf Of Pankaj Aggarwal >> Sent: 04 April 2010 12:46 >> To: openssl-users@openssl.org >> Subject: Re: OpenSSL on IBMi >> >> I used the patch on openssl 0.9.8e. on firing ./Configure OS400-icc I am getting the following error: >> >> qsh: 001-0014 Command /home/qsecofr/openssl/QAPTL/GMAKE not found. >> GMAKE: *** [links] Error 1 >> $ >> >> I have set the PATH environment variable as follows : >> >> /qibm/ProdData/DeveloperTools/qsh/bin/:/usr/bin:.:/QOpenSys/usr/bin >> >> I am using the old perl binaries for OS400 from CPAN site. >> >> Any idea where the problem is? >> >> On Sun, Apr 4, 2010 at 3:08 PM, Shaw Graham George <gs...@axway.com> wrote: >>> >>> http://rt.openssl.org/Ticket/Display.html?id=1565&user=guest&pass=gues >>> t >>> >>> Only for 0.9.8e, though. >>> >>> G. >>> >>> >>> -----Original Message----- >>> From: owner-openssl-us...@openssl.org >>> [mailto:owner-openssl-us...@openssl.org] On Behalf Of Pankaj Aggarwal >>> Sent: 04 April 2010 10:05 >>> To: openssl-users@openssl.org >>> Subject: OpenSSL on IBMi >>> >>> Could somebody point me to the latest patch available (with >>> instructions) for compiling openssl on IBMi (OS/400). >>> >>> Pankaj >>> ______________________________________________________________________ >>> OpenSSL Project http://www.openssl.org >>> User Support Mailing List openssl-users@openssl.org >>> Automated List Manager majord...@openssl.org >>> ______________________________________________________________________ >>> OpenSSL Project http://www.openssl.org >>> User Support Mailing List openssl-users@openssl.org >>> Automated List Manager majord...@openssl.org >>> >> ______________________________________________________________________ >> OpenSSL Project http://www.openssl.org >> User Support Mailing List openssl-users@openssl.org >> Automated List Manager majord...@openssl.org >> ______________________________________________________________________ >> OpenSSL Project http://www.openssl.org >> User Support Mailing List openssl-users@openssl.org >> Automated List Manager majord...@openssl.org >> > ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List openssl-users@openssl.org Automated List Manager majord...@openssl.org
