Re: using ./Configure to generate listing files
That is part of why I use a separate shell script to do this. I parse the
parameters and pull the filename into a variable using sed options. Then I can
build a listing file name and specify it in the actual c89/xlc command.
For example, this builds a C listing filename:
sname3=`echo $argshift1|sed 's/\.o/.lc/g'`
Lloyd
From: Janet Graff janet.gr...@yahoo.com
To: IBM-MAIN@LISTSERV.UA.EDU
Sent: Tuesday, November 5, 2013 2:15 PM
Subject: Re: using ./Configure to generate listing files
The -Wc,LIST(filename) option would work fine to indicate that I want a
listing file. But without a file name it defaults to STDOUT. The specific
filename doesn't adjust for different source code files. Is there a
replacement variable for ./Configure that says use the source code file name
so that I can add something like -Wc,LIST(${source}) to my options and get a
seperate listing file for each source file?
Janet
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: using ./Configure to generate listing files
If this is a z/OS system consider AT-TLS instead of openssl. Mike Wawiorko Please consider the environment before printing this e-mail -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Janet Graff Sent: 04 November 2013 17:25 To: IBM-MAIN@LISTSERV.UA.EDU Subject: using ./Configure to generate listing files I am attempting to build openssl on the mainframe. Can I set up my ./Configure OS390 line to generate a listing file for every module compiled? I need something like this OS/390,c99:-O -Wc,ascii -Wc,LIST(fname.LIST) -DB_ENDIAN -DNO_SYS_PARAM_H -D_ALL_SOURCE -DASCII -D_XOPEN_SOURCE_EXTENDED=1 -D_XOPEN_SOURCE=500 -D_POSIX_SOURCE -D_OPEN_THREADS=2 -DOPENSSL_EXPORT_VAR_AS_FUNCTION::-DPTHREAD:::THIRTY_TWO_BIT DES_PTR DES_UNROLL MD2_CHAR RC4_INDEX RC4_CHAR BF_PTR:::, where the fname on the LIST option is whatever the name of the currently compiling module is. Is this not the way to do this? Is there a better way? Janet Graff -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN This e-mail and any attachments are confidential and intended solely for the addressee and may also be privileged or exempt from disclosure under applicable law. If you are not the addressee, or have received this e-mail in error, please notify the sender immediately, delete it from your system and do not copy, disclose or otherwise act upon any part of this e-mail or its attachments. Internet communications are not guaranteed to be secure or virus-free. The Barclays Group does not accept responsibility for any loss arising from unauthorised access to, or interference with, any Internet communications by any third party, or from the transmission of any viruses. Replies to this e-mail may be monitored by the Barclays Group for operational or business reasons. Any opinion or other information in this e-mail or its attachments that does not relate to the business of the Barclays Group is personal to the sender and is not given or endorsed by the Barclays Group. Barclays Bank PLC. Registered in England and Wales (registered no. 1026167). Registered Office: 1 Churchill Place, London, E14 5HP, United Kingdom. Barclays Bank PLC is authorised by the Prudential Regulation Authority and regulated by the Financial Conduct Authority and the Prudential Regulation Authority (Financial Services Register No. 122702). -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: using ./Configure to generate listing files
Janet, Take a look at the archives for this list, specifically the thread: openssl make - z/OS UNIX question - Help from April 2012. Kirk Wolf Dovetailed Technologies http://dovetail.com On Mon, Nov 4, 2013 at 11:24 AM, Janet Graff janet.gr...@yahoo.com wrote: I am attempting to build openssl on the mainframe. Can I set up my ./Configure OS390 line to generate a listing file for every module compiled? I need something like this OS/390,c99:-O -Wc,ascii -Wc,LIST(fname.LIST) -DB_ENDIAN -DNO_SYS_PARAM_H -D_ALL_SOURCE -DASCII -D_XOPEN_SOURCE_EXTENDED=1 -D_XOPEN_SOURCE=500 -D_POSIX_SOURCE -D_OPEN_THREADS=2 -DOPENSSL_EXPORT_VAR_AS_FUNCTION::-DPTHREAD:::THIRTY_TWO_BIT DES_PTR DES_UNROLL MD2_CHAR RC4_INDEX RC4_CHAR BF_PTR:::, where the fname on the LIST option is whatever the name of the currently compiling module is. Is this not the way to do this? Is there a better way? Janet Graff -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: using ./Configure to generate listing files
Kirk, Yes! That excellent thread is what enabled me to get as far as I did and produce my needed libcrypto.a library. I've been through that thread multiple times in the last three weeks but I don't recall a discussion of changing the ./Configure settings to produce listing files for every source code module compiled during the make phase. Do you know that there is a reference to listing files in that thread (in which case I will go back through the thread again line by line) or was that a reference to general topic equivalence? Thanks! Janet -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: using ./Configure to generate listing files
Mike, This particular usage of openssl is specifically for the bignum support. AT-TLS is for the SSL support which we aren't using. Do you know of a bignum replacement for openssl for z/OS? Janet -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: using ./Configure to generate listing files
Janet, When I have some options that are not part of the normal, I specify a different shell script for compiling (like xlc64.sh for example), and specify that as the compiler in ./configure or make or whatever. Then that shell script calls the compiler once it has set up things like I want. This allows me to test new options without breaking existing things: just comment the real compiler name and specify the new one. Then to reverse things, uncomment the real compiler and comment the new one. Lloyd From: Janet Graff janet.gr...@yahoo.com To: IBM-MAIN@LISTSERV.UA.EDU Sent: Tuesday, November 5, 2013 11:46 AM Subject: Re: using ./Configure to generate listing files Kirk, Yes! That excellent thread is what enabled me to get as far as I did and produce my needed libcrypto.a library. I've been through that thread multiple times in the last three weeks but I don't recall a discussion of changing the ./Configure settings to produce listing files for every source code module compiled during the make phase. Do you know that there is a reference to listing files in that thread (in which case I will go back through the thread again line by line) or was that a reference to general topic equivalence? Thanks! Janet -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: using ./Configure to generate listing files
The -Wc,LIST(filename) option would work fine to indicate that I want a
listing file. But without a file name it defaults to STDOUT. The specific
filename doesn't adjust for different source code files. Is there a
replacement variable for ./Configure that says use the source code file name
so that I can add something like -Wc,LIST(${source}) to my options and get a
seperate listing file for each source file?
Janet
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: using ./Configure to generate listing files
I don't see anything like that in the Makefile.
I'm far from an export on make, and the OpenSSL Makefile is pretty nasty.
My best guess is that you need to define your own inference rule something
like:
%.o : %.c
$(CC) -c $(CCFLAGS) -Wc,LIST $ $*.list
Kirk Wolf
Dovetailed Technologies
http://dovetail.com
On Tue, Nov 5, 2013 at 1:15 PM, Janet Graff janet.gr...@yahoo.com wrote:
The -Wc,LIST(filename) option would work fine to indicate that I want a
listing file. But without a file name it defaults to STDOUT. The specific
filename doesn't adjust for different source code files. Is there a
replacement variable for ./Configure that says use the source code file
name so that I can add something like -Wc,LIST(${source}) to my options
and get a seperate listing file for each source file?
Janet
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: using ./Configure to generate listing files
On Tue, 5 Nov 2013 13:33:37 -0600, Kirk Wolf wrote: I don't see anything like that in the Makefile. I'm far from an export on make, and the OpenSSL Makefile is pretty nasty. My best guess is that you need to define your own inference rule something like: %.o : %.c $(CC) -c $(CCFLAGS) -Wc,LIST $ $*.list One of the problems I've had doing this sort of thing is that the options to c89 require the use of shell metacharacters. This is made worse because ./configure has (at least) two different passes, one of which evaluates the command through one more level than the other, frustrating any attempt to quote the metacharacters. But that was long ago; perhaps xlc has become more configure-friendly. At that time, I concluded that the IBM designers really didn't care about the GNU expectations. -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
using ./Configure to generate listing files
I am attempting to build openssl on the mainframe. Can I set up my ./Configure OS390 line to generate a listing file for every module compiled? I need something like this OS/390,c99:-O -Wc,ascii -Wc,LIST(fname.LIST) -DB_ENDIAN -DNO_SYS_PARAM_H -D_ALL_SOURCE -DASCII -D_XOPEN_SOURCE_EXTENDED=1 -D_XOPEN_SOURCE=500 -D_POSIX_SOURCE -D_OPEN_THREADS=2 -DOPENSSL_EXPORT_VAR_AS_FUNCTION::-DPTHREAD:::THIRTY_TWO_BIT DES_PTR DES_UNROLL MD2_CHAR RC4_INDEX RC4_CHAR BF_PTR:::, where the fname on the LIST option is whatever the name of the currently compiling module is. Is this not the way to do this? Is there a better way? Janet Graff -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
