Re: PLEASE TEST: Latest cygwin snapshot == 1.5.10 alpha

2004-05-25 Thread Igor Pechtchanski
On Wed, May 19, 2004 at 06:08:01PM -0400, Igor Pechtchanski wrote: I'm sorry to report that the problem I described in http://cygwin.com/ml/cygwin/2004-05/msg00596.html (multiple xterms started in quick succession get the same PTY) still exists in the 20040519 snapshot. The output of ps

PLEASE TEST: Latest Cygwin snapshot == 1.5.10 alpha

2004-05-20 Thread Corinna Vinschen
Hi, since we're heading with big steps towards Cygwin version 1.5.10, I'd like to encourage as many of you as possible to give the latest developer snapshot a test. http://cygwin.com/snapshots/ Many bugfixes and some interesting changes have been made and some new functionality have been

Re: PLEASE TEST: Latest Cygwin snapshot == 1.5.10 alpha

2004-05-20 Thread Igor Pechtchanski
On Thu, 20 May 2004, Corinna Vinschen wrote: Hi, since we're heading with big steps towards Cygwin version 1.5.10, I'd like to encourage as many of you as possible to give the latest developer snapshot a test. http://cygwin.com/snapshots/ Many bugfixes and some interesting changes have

Re: PLEASE TEST: Latest Cygwin snapshot == 1.5.10 alpha

2004-05-20 Thread Corinna Vinschen
On May 20 09:22, Igor Pechtchanski wrote: BTW, should /dev/kmem work also? No, only /dev/mem and /dev/port are working. /dev/kmem is still looking for a contributor. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Co-Project Leader

Re: PLEASE TEST: Latest Cygwin snapshot == 1.5.10 alpha

2004-05-20 Thread Eric Hanchrow
For what it's worth, the snapshot appears to fix a problem that I've had building CVS guile -- briefly: the built guile would (when used to build the documentation) immediately die with an error message from Windows. I'd be happy to provide more details if anyone's interested. -- If you can't

Re: PLEASE TEST: Latest cygwin snapshot == 1.5.10 alpha

2004-05-20 Thread Christopher Faylor
On Thu, May 20, 2004 at 09:22:28AM -0400, Igor Pechtchanski wrote: - Fix problem where simultaneous attempts to open new ptys could lead to the same pty being opened multiple times. (Christopher Faylor) As I've reported already, this isn't entirely fixed. Sigh. My new email setup really