This is the mail archive of the
cygwin@cygwin.com
mailing list for the Cygwin project.
RE: Pipe "make" stdout and stderr to process?
- To: "'cygwin at cygwin dot com'" <cygwin at cygwin dot com>
- Subject: RE: Pipe "make" stdout and stderr to process?
- From: "Karr, David" <david dot karr at cacheflow dot com>
- Date: Thu, 5 Jul 2001 15:10:12 -0700
That did it, thanks. I didn't notice an example of this in the Bash man
page.
-----Original Message-----
From: Randall R Schulz [mailto:rrschulz@cris.com]
Sent: Thursday, July 05, 2001 3:01 PM
To: Karr, David; 'cygwin@cygwin.com'
Subject: Re: Pipe "make" stdout and stderr to process?
David,
It's somewhat counterintuitive by comparison to the ordering required in
the absence of a pipe, but you have to merge stderr (2) into stdout (1)
before the pipe symbol:
make 2>&1 |filterprog
Randall Schulz
At 14:13 2001-07-05, Karr, David wrote:
>How do I run "make" so I can pass both stdout and stderr to a filtering
>process? I'm familiar with writing the output to a file, taking both
stdout
>and stderr ("make > make.out 2>&1"), but I don't see how to get this to
work
>if I just want to pipe the output (both stdout and stderr) to another
>process. When I do "make | filterprog 2>&1", it seems to have no effect,
in
>that it appears as if the stderr from "make" goes directly to the console.
> >From reading the "bash" man page, it almost seems as if redirection
doesn't
>apply to piping.
>
>--
>Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
>Bug reporting: http://cygwin.com/bugs.html
>Documentation: http://cygwin.com/docs.html
>FAQ: http://cygwin.com/faq/
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/