From: fjh@cs.mu.OZ.AU (Fergus Henderson)
Subject: Re: Catching g++ error output
18 Apr 1997 04:22:05 -0700
Approved: cygnus.gnu-win32@cygnus.com
Distribution: cygnus
Message-ID: <199704181052.UAA13341.cygnus.gnu-win32@mundook.cs.mu.OZ.AU>
Content-Type: text
Original-To: jpmorgan@unm.edu (James Paul Morgan)
Original-Cc: gnu-win32@cygnus.com (Cygnus GNU-win32 mailing list)
In-Reply-To: <Pine.A32.3.91.970418010547.20142E-100000@pegasus.unm.edu> from "James Paul Morgan" at Apr 18, 97 01:11:07 am
X-Mailer: ELM [version 2.4 PL24]
Original-Sender: owner-gnu-win32@cygnus.com

James Paul Morgan, you wrote:
> 
> Is there any way to capture the error output from g++ when it fails on a 
> compile?

In bash:

	gcc ... >& error-file

or

	gcc ... 2>&1 | tee error-file

-- 
Fergus Henderson <fjh@cs.mu.oz.au>   |  "I have always known that the pursuit
WWW: <http://www.cs.mu.oz.au/~fjh>   |  of excellence is a lethal habit"
PGP: finger fjh@128.250.37.3         |     -- the last words of T. S. Garp.
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".
