Terri, We recently did a port of OpenSSL (0.9.8k I believe), and there are a few things that you will need to do. (Note: in our port, the crypto/evp library worked fine, but there were some ASCII issues in the tools/commands that we didn't attempt to resolve.)
Here are some notes, but be forewarned that this is tricky stuff. If you haven't worked with the GNU toolchain and z/OS Unix extensively, you make want to get help. Some prereqs: - perl from IBM Ported Tools for z/OS or your own port - gmake -- setup: - assuming that perl and gmake are in /usr/local/bin, add /usr/local/bin to your your PATH after /bin - export MAKE=gmake - chmod +x tools/* -- configure and make ./config --prefix=/usr/local --openssldir=/usr/local/openssl export _C89_CCMODE=1 export MAKE=gmake $MAKE On Tue, Apr 3, 2012 at 10:25 AM, Shaffer, Terri E < [email protected]> wrote: > Hi, > > I have cross-posted this on the MVS-OE page but hope someone can help me > here... > > I am having an issue with doing a make on building a newer version on > openssl. I download the new tar from openssl.orq and have it exploded to > my directory. I then changed to the ssl directory and can see the > descriptor file called Makefile. What I am trying to do now is build the > new version of openssl and having issues. When I issue the make -f Makefile > openssl it uses lots of cpu but never seems to finish and/or build anything > and I am at a loss. > > Can anyone Please shed some light on where I took a wrong turn or how to > do this? > > Thanks > > Ms. Terri E. Shaffer > [email protected] > Engineer > J.P.Morgan Chase & Co. > GTI DCT ECS Core Services zSoftware Group / Emerging Technologies > Office: # 614-213-3467 > Cell: # 412-519-2592 > This communication is for informational purposes only. It is not > intended as an offer or solicitation for the purchase or sale of > any financial instrument or as an official confirmation of any > transaction. All market prices, data and other information are not > warranted as to completeness or accuracy and are subject to change > without notice. Any comments or statements made herein do not > necessarily reflect those of JPMorgan Chase & Co., its subsidiaries > and affiliates. > > This transmission may contain information that is privileged, > confidential, legally privileged, and/or exempt from disclosure > under applicable law. If you are not the intended recipient, you > are hereby notified that any disclosure, copying, distribution, or > use of the information contained herein (including any reliance > thereon) is STRICTLY PROHIBITED. Although this transmission and any > attachments are believed to be free of any virus or other defect > that might affect any computer system into which it is received and > opened, it is the responsibility of the recipient to ensure that it > is virus free and no responsibility is accepted by JPMorgan Chase & > Co., its subsidiaries and affiliates, as applicable, for any loss > or damage arising in any way from its use. If you received this > transmission in error, please immediately contact the sender and > destroy the material in its entirety, whether in electronic or hard > copy format. Thank you. > > Please refer to http://www.jpmorgan.com/pages/disclosures for > disclosures relating to European legal entities. > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
