And only now I've found the messages talking about similar issues after
fruitless Google searches. Same thing happens to me after I buy hardware.
The problem appears fixed in the latest snapshot of cygwin1.dll.
Indeed it was; the problem happened for at least two other people on the
mailing
Further to my previous email: I should add that redirected output works
fine.
$ ./err.exe 2/dev/null
$ ./err.exe 2out.txt
Either works fine, and the contents of out.txt are as expected.
Barry Kelly wrote:
This C# app:
class err
{
static void Main()
{
And only now I've found the messages talking about similar issues after
fruitless Google searches. Same thing happens to me after I buy
hardware.
The problem appears fixed in the latest snapshot of cygwin1.dll.
Sigh.
Barry Kelly wrote:
Further to my previous email: I should add that
Hi,
I've discovered some odd behaviour with make v3.79.1 as included with the CygWin
development tools package. I've searched the web and checked the make manual, but have
not been able to find anything helpful so far.
When calling ccppc (a PowerPC cross-compiler supplied as part of the
On 10 Jan 2002 at 20:55, Gary R. Van Sickle wrote:
[cgf wrote:]
If this doesn't do it, then I think the best plan is to find help from
another mailing list. Basic shell questions are not really appropriate
here -- especially given the recent volume we've been experiencing.
I've been
A while ago I was helping students that were new
to bash and UNIX and I wrote a little guide in HTML.
Late I put together Cygwin-Lite (Cygwin on a floppy)
and added the guide. This was before the setup.exe
changes that made a minimal install easy. I've
stopped updating Cygwin-Lite but I think
At 09:55 PM 1/10/2002, Gary R. Van Sickle wrote:
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf
Of Christopher Faylor
[snip]
For Bourne style shells I use
runme filename 21
This redirects stdout first and then stderr to whereever
Anything sent to stderr does not appear on the terminal. It seems to
disappear into a black hole. I think it started when I was attempting to
redirect stdout and stderr into the same file in the same order it appears
on the console using something like
runme 12 filename
I tried all sorts of
At 05:07 PM 1/10/2002, William S Fulton wrote:
Anything sent to stderr does not appear on the terminal. It seems to
disappear into a black hole. I think it started when I was attempting to
redirect stdout and stderr into the same file in the same order it appears
on the console using something
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf
Of Christopher Faylor
[snip]
For Bourne style shells I use
runme filename 21
This redirects stdout first and then stderr to whereever stdout is
pointing.
If this doesn't do it, then I think the
===
- Original Message -
From: Gary R. Van Sickle [EMAIL PROTECTED]
Comments? Questions other than what are you smoking? ;-)
How long have you been somking it :}-.
Rob
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:
11 matches
Mail list logo
