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 <[email protected]> >To: [email protected] >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 [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
