At 12:12 AM -0400 4/9/04, John E. Malmberg wrote:
>It appears that the configure -s option is incompatible with having the configure
>script being run from a wrapper command file with the output redirected to a log file.
Hmm. Guess I've never tried that since I generally build in batch and get a log that
way.
>
>Removing the -s option results in prompts to continue.
>
>For example for a command file:
>
>$!
>$if f$search("''build_disk'[''root']config.h") .eqs. ""
>$then
>$show time
>$ @'build_disk'['root']configure.com "-de"
>$! @build_root:['root']configure.com -"Dusevmsdebug" "-de"
>$show time
>$endif
>
>
>
>EAGLE> @LOCAL_ROOT:[000000]build_gnv_perl.com/out=build.log
>Type carriage return to continue
>Type carriage return to continue
>Type carriage return to continue
These are done with READ/PROMPT. What happens if you do DEFINE SYS$COMMAND SYS$INPUT
before running?
--
________________________________________
Craig A. Berry
mailto:[EMAIL PROTECTED]
"... getting out of a sonnet is much more
difficult than getting in."
Brad Leithauser
