Fwd: Re: B20: stdio bugs with 'merge' & 'gzip'
Earnie Boyd
earnie_boyd@yahoo.com
Fri Dec 3 17:15:00 GMT 1999
Note: forwarded message attached.
=====
Earnie Boyd < mailto:earnie_boyd@yahoo.com >
Cygwin Newbies, please visit
< http://www.freeyellow.com/members5/gw32/index.html >
__________________________________________________
Do You Yahoo!?
Thousands of Stores. Millions of Products. All in one place.
Yahoo! Shopping: http://shopping.yahoo.com
To : <earnie_boyd at yahoo dot com>
Subject : Re: B20: stdio bugs with 'merge' & 'gzip'
>From : "Dmitry Karasik" <dk at plab dot ku dot dk>
Date : Fri, 3 Dec 1999 23:53:56 +0100
References : < 19991203185238.18088.qmail@web106.yahoomail.com >
Hi Earnie!
> The essence of the page states that yes, there is a bug in processing the
of
> pipes and redirection (and therefore the stdio routines) for the stock
> cygwin1.dll. You need to upgrade with at least the Jan 15th, 1999
snapshot.
> You may find this and more current snapshots at
> http://sourceware.cygnus.com/cygwin/snapshots/ .
> You still need to modify your path and get rid of multiple cygwin dlls.
But,
> to not do so is your choice.
And still the solution is as far as week ago. I took the very last
cygwin1.dll - from 02-Dec-99,
I removed all dlls from path, and no difference. The only thing maybe will
give a clue:
every b20-compiled program complains now:
0 0 [main] C:\-\-\a.exe 1000 hinfo_init: couldn't make stderr distinct
from stdout
I don't know, how to contact actual developers, but if you know, tell them
that
the bug not WAS, it IS. I have to thank you for your patience and help, but
I want to know -
is that particular bug is only on my machine or not? If it's not mine, how
ever you could not
notice that bug? It's everyday tools, - gzip, merge, echo, diff ...
Sincerely,
Dmitry
More information about the Cygwin
mailing list