Re: configure -s option incompatible with /output=log.file

Craig A. Berry wrote:
> 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.
> > 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
[return pressed]
>> Type carriage return to continue
[return pressed]
>> Type carriage return to continue
[return pressed]
> These are done with READ/PROMPT.  What happens if you do DEFINE
> SYS$COMMAND SYS$INPUT before running?
No change in behavior.  I will look into this later.

From your description, if I submit this procedure to batch, it will 
probably work ok.
-John
wb8tyw@xxxxxxxxxxx
Personal Opinion Only