public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Alexander Osipenko" <sip@cos.ru>
To: cygwin@cygwin.com
Subject: Re: cygwin 1.5+  process control  problem?
Date: Tue, 23 Sep 2003 08:01:00 -0000	[thread overview]
Message-ID: <bkou8l$eln$1@sea.gmane.org> (raw)
In-Reply-To: <20030923040441.GB26127@redhat.com>

Thanks, the snapshot cygwin1-20030923.dll.bz2 works.
Alexander.

"Christopher Faylor" <cgf-rcm@cygwin.com> wrote in message
news:20030923040441.GB26127@redhat.com...
> On Tue, Sep 23, 2003 at 06:37:07AM +0400, Alexander Osipenko wrote:
> >Shell hangs, executing command
> >
> >$ gcc -v --help | less
>
> >Behavior noticed in
> >  cygwin-1.5.4-1
> >  gcc-3.2-3
> >  bash-2.05b-13
> >  less-381-1
> >
> >and remains after each upgrade until current version:
> >  cygwin-1.5.5-1
> >  gcc-3.3.1-1
> >  bash-2.05b-13
> >  less-381-1
> >
> >I can say nothing about cygwin 1.4+, but in other machine with cygwin-1.3.22-1 all
> >operates as expected
>
> I wished you'd reported this when you noticed it in 1.5.4.  I would have fixed it
> for 1.5.5.
>
> >Perhaps, similar behavior mentioned in
> >http://cygwin.com/ml/cygwin/2003-09/msg00992.html
>
> No.  I reported that problem was fixed.  If you suspected that it was
> related then downloading a snapshot and trying it would have been very
> helpful for the cygwin cause.
>
> Anyway, it should be fixed in the next snapshot.
>
> http://cygwin.com/ , click on "Snapshots".
>
> cgf
>




--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

      reply	other threads:[~2003-09-23  7:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-23  3:19 Alexander Osipenko
2003-09-23  4:08 ` Christopher Faylor
2003-09-23  8:01   ` Alexander Osipenko [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='bkou8l$eln$1@sea.gmane.org' \
    --to=sip@cos.ru \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).