Sorry about that, here is the beginning. I also pasted some of the hex code and
what I think would be hex20 (ascii spaces) are hex09 as the first char. Not
sure what an HT is.
PREFIX=""
SUFFIX=""
TEST="false"
EXE=""
# pick up any command line args to config
for i
do
case "$i" in
-d*) PREFIX="debug-";;
-t*) TEST="true";;
-h*) TEST="true"; cat <<EOF
Usage: config [options]
-d Add a debug- prefix to machine choice.
-t Test mode, do not run the Configure perl script.
-h This help.
Any other text will be passed to the Configure perl script.
See INSTALL for instructions.
EOF
;;
*) options=$options" $i" ;;
esac
done
# First get uname entries that we use below
[ "$MACHINE" ] || MACHINE=`(uname -m) 2>/dev/null` || MACHINE="unknown"
[ "$RELEASE" ] || RELEASE=`(uname -r) 2>/dev/null` || RELEASE="unknown"
[ "$SYSTEM" ] || SYSTEM=`(uname -s) 2>/dev/null` || SYSTEM="unknown"
[ "$BUILD" ] || VERSION=`(uname -v) 2>/dev/null` || VERSION="unknown"
000064 case "$XREL" in
066762225544226622222222222222222222222222222222222222222222222222222222
93135024825C209E00000000000000000000000000000000000000000000000000000000
------------------------------------------------------------------------------
000065 4.0|4.1)
022223237323222222222222222222222222222222222222222222222222222222222222
900004E0C4E1900000000000000000000000000000000000000000000000000000000000
------------------------------------------------------------------------------
000066 echo "${MACHINE}-whatever-isc4"; exit 0
002222666622274444444727667676726763232676723222222222222222222222222222
990000538F024BD1389E5DD78145652D93342B0589400000000000000000000000000000
------------------------------------------------------------------------------
000067 ;;
003322222222222222222222222222222222222222222222222222222222222222222222
99BB00000000000000000000000000000000000000000000000000000000000000000000
------------------------------------------------------------------------------
000068 esac
067662222222222222222222222222222222222222222222222222222222222222222222
953130000000000000000000000000000000000000000000000000000000000000000000
To answer Kirk's question. I did have trouble unwinding the tarball
I finally used tar -xf openssl-1.0.1.tar
I am not sure I did the set correctly. I need the unix for dummies book about
now.
W012108:SDEV(DEV):/u/w012108/temp/openssl-1.0.1 > set -x
W012108:SDEV(DEV):/u/w012108/temp/openssl-1.0.1 > ./config --prefix=/usr/local -
-openssldir=/usr/local/openssl
+ ./config --prefix=/usr/local --openssldir=/usr/local/openssl
./config 1: syntax error: got ), expecting Newline
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
>
> -----Original Message-----
> From: IBM Mainframe Discussion List [mailto:[email protected]] On
> Behalf Of Kirk Wolf
> Sent: Tuesday, April 03, 2012 3:11 PM
> To: [email protected]
> Subject: Re: openssl make - z/OS UNIX question - Help
>
> Do this first:
> ./config --prefix=/usr/local --openssldir=/usr/local/openssl
>
> and after the configure script runs, then do the make:
>
> $MAKE
>
> But I'm now retreating to my original position :-)
>
>
> On Tue, Apr 3, 2012 at 1:23 PM, Shaffer, Terri E <
> [email protected]> wrote:
>
>> Hi Kirk,
>> Okay you are right I do see the config file..
>>
>> W012108:SDEV(DEV):/u/w012108/temp/openssl-1.0.1 > chmod +x tools/*
>> W012108:SDEV(DEV):/u/w012108/temp/openssl-1.0.1 > export MAKE=gmake
>> W012108:SDEV(DEV):/u/w012108/temp/openssl-1.0.1 > export
>> _C89_CCMODE=1
>> W012108:SDEV(DEV):/u/w012108/temp/openssl-1.0.1 > ./config
>> --prefix=/usr/local --openssldir=/usr/local/openssl $MAKE ./config 1:
>> syntax error: got ), expecting Newline
>> W012108:SDEV(DEV):/u/w012108/temp/openssl-1.0.1 >
>>
>> I am executing the 1.0.1 version as on March 14.
>>
>> I'm sorry my Perl experience is non-existent, so yet another limitation.
>>
>> Any idea of why I would get the syntax error? Or did I do something wrong.
>>
>> Thank for you help!
>>
>> 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
>>
>>
>> -----Original Message-----
>> From: IBM Mainframe Discussion List [mailto:[email protected]] On
>> Behalf Of Kirk Wolf
>> Sent: Tuesday, April 03, 2012 1:59 PM
>> To: [email protected]
>> Subject: Re: openssl make - z/OS UNIX question - Help
>>
>> Terri,
>>
>> I see both "config" and "Configure" in openssl 0.9.8q
>>
>> "config" is a shell script, that starts:
>>
>> #!/bin/sh
>> #
>> # OpenSSL config: determine the operating system and run ./Configure
>> # # "config -h" for usage information.
>> ...
>>
>> So, config is a front end to the Configure perl script.
>>
>> Kirk Wolf
>> Dovetailed Technologies
>> http://dovetail.com
>>
>> On Tue, Apr 3, 2012 at 12:28 PM, Shaffer, Terri E <
>> [email protected]> wrote:
>>
>> > Thanks Kirk,
>> > LOL, Yes I am in slightly over my head, but that another political
>> > story as far as that help goes.
>> >
>> > If I look at where I exploded the tarball I see a Configure file
>> > that I see is expecting the over-rides you mention.
>> >
>> > Configure Viewed File rwxrwxr-x
>> >
>> > I also have gmake so I can utilize that, I must be doing something
>> > else wrong so here are my steps.
>> >
>> > export MAKE=gmake
>> > export _C89_CCMODE=1
>> > ./Configure --prefix=/usr/local --openssldir=/usr/local/openssl
>> >
>> > I'm guessing this part was a repeat of the setup MAKE=gmake $MAKE
>> >
>> > Then the $MAKE has the gmake assigned to it.
>> >
>> > Here's where I get more lost. What actually starts the process or
>> > starts the Configure or Makefile?
>> >
>> > Can you hopefully fill in my blanks?
>> >
>> > 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
>> >
>> >
>> > -----Original Message-----
>> > From: IBM Mainframe Discussion List [mailto:[email protected]]
>> > On Behalf Of Kirk Wolf
>> > Sent: Tuesday, April 03, 2012 11:51 AM
>> > To: [email protected]
>> > Subject: Re: openssl make - z/OS UNIX question - Help
>> >
>> > 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
