Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Message-Id: <5.1.0.14.2.20010705145836.025ed008@pop3.cris.com> X-Sender: rrschulz AT pop3 DOT cris DOT com X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Thu, 05 Jul 2001 15:00:44 -0700 To: "Karr, David" , "'cygwin AT cygwin DOT com'" From: Randall R Schulz Subject: Re: Pipe "make" stdout and stderr to process? In-Reply-To: <2C08D4EECBDED41184BB00D0B74733420473EDEE@exchanger.cachefl ow.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed 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/