This is the mail archive of the
cygwin@sources.redhat.com
mailing list for the Cygwin project.
Re: One more detail on bash behaviour
- To: Cygwin mailing list <Cygwin at sources dot redhat dot com>
- Subject: Re: One more detail on bash behaviour
- From: Chris Faylor <cgf at cygnus dot com>
- Date: Wed, 18 Oct 2000 15:39:30 -0400
- References: <001201c038f2$8a28e1b0$21c9ca95@mow.siemens.ru>
- Reply-To: cygwin at sources dot redhat dot com
On Wed, Oct 18, 2000 at 02:59:51PM +0400, Andrej Borsenkow wrote:
>I typed "make install" (guess, what :-) and, first, bash prompt appeared, and
>THEN make output started:
>
>mw1g017@MW1G17C /tools/build/zsh
>$ make install
>
>mw1g017@MW1G17C /tools/build/zsh
>$ make[1]: Entering directory `/tools/build/zsh/Src'
>Linking with the standard modules.
>make[2]: Entering directory `/tools/build/zsh/Src'
>make[3]: Entering directory `/tools/build/zsh/Src/Builtins'
>make[3]: Leaving directory `/tools/build/zsh/Src/Builtins'
>make[3]: Entering directory `/tools/build/zsh/Src/Modules'
>...
>
>How bash finds out that child exited? It starts to look the hell like
>bash bug to me. And even if it is cygwin race condition, it is not in
>tty handling.
It's a cygwin bug. Should be fixed in 2000-Oct-17 snapshot.
cgf
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com