This is the mail archive of the cygwin-developers mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: More: [1.7] packaging problem? Both /usr/bin/ and /usr/lib/ are non-empty


On May 13 11:07, Corinna Vinschen wrote:
> On May 12 23:13, Christopher Faylor wrote:
> > On Tue, May 12, 2009 at 07:42:25PM -0600, Eric Blake wrote:
> > >According to Christopher Faylor on 5/12/2009 7:22 PM:
> > >>> In other words, if stdin and stderr are both ttys, then it seems like
> > >>> posix requires both forms
> > >> 
> > >> The change that I made to setup.exe opens stdout as a console if a
> > >> console exists.  Could that be causing the problem?
> > >
> > >For bash, stdout is not the issue; it is stdin and stderr that determine
> > >interactivity.
> > 
> > Hmm.  Looking at setup's run() function, stdin *should* be set to an
> > INVALID_HANDLE_VALUE when a process is Created but I wonder if there is
> > something odd going on on regardless.
> 
> But si.hStdError is set to the console handle in run().

Ouch, ignore this.  Stdout and stderr are redirected to the log file,
of course, not to the console.  status = STATUS_NOT_ENOUGH_COFFEE.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]