Re: run: requires CYGWIN=tty?

2009-11-26 Thread Corinna Vinschen
On Nov 25 23:44, Charles Wilson wrote: Yaakov (Cygwin/X) wrote: I came across this error with run when launched from the cmd prompt with an empty CYGWIN variable: 1 [main] xterm 1248 dtable::stdio_init: couldn't make stderr distinct from stdout If I set CYGWIN=tty then this

Re: run: requires CYGWIN=tty?

2009-11-26 Thread Corinna Vinschen
On Nov 26 10:35, Corinna Vinschen wrote: However, Chuck, can you please try the below patch to run.c instead? It makes the stdout and stderr handles already distinct in run: Index: src/run.c === RCS file:

Re: run: requires CYGWIN=tty?

2009-11-26 Thread Charles Wilson
Corinna Vinschen wrote: On Nov 26 10:35, Corinna Vinschen wrote: However, Chuck, can you please try the below patch to run.c instead? It makes the stdout and stderr handles already distinct in run: I can't reproduce the problem with the original run (my xterm dumps core, for a different

run: requires CYGWIN=tty?

2009-11-25 Thread Yaakov (Cygwin/X)
Chuck, I came across this error with run when launched from the cmd prompt with an empty CYGWIN variable: 1 [main] xterm 1248 dtable::stdio_init: couldn't make stderr distinct from stdout If I set CYGWIN=tty then this does not occur. Is this expected? Yaakov -- Problem reports:

Re: run: requires CYGWIN=tty?

2009-11-25 Thread Charles Wilson
Yaakov (Cygwin/X) wrote: I came across this error with run when launched from the cmd prompt with an empty CYGWIN variable: 1 [main] xterm 1248 dtable::stdio_init: couldn't make stderr distinct from stdout If I set CYGWIN=tty then this does not occur. Is this expected? Not by me.