From:	trout AT sci DOT fi (Antti Harju)
Subject:	Re: Catching g++ error output
18 Apr 1997 12:05:02 -0700 :
Sender:	mail AT cygnus DOT com
Approved:	cygnus DOT gnu-win32 AT cygnus DOT com
Distribution:	cygnus
Message-ID:	<3.0.1.32.19970418182640.006d29b8.cygnus.gnu-win32@sci.fi>
References:	<Pine DOT SUN DOT 3 DOT 96 DOT 970417185746 DOT 15874C-100000 AT tlaloc DOT stat DOT colostate DOT edu>
X-Sender:	trout AT sci DOT fi
X-Mailer:	Windows Eudora Pro Version 3.0.1 (32)
Original-To:	gnu-win32 AT cygnus DOT com
Original-Cc:	James Paul Morgan <jpmorgan AT unm DOT edu>
In-Reply-To:	<Pine.A32.3.91.970418010547.20142E-100000@pegasus.unm.edu>
Mime-Version:	1.0
Original-Sender:	owner-gnu-win32 AT cygnus DOT com

At 01:11 18.4.1997 -0600, you wrote:
>Is there any way to capture the error output from g++ when it fails on a 
>compile?  Sometimes, a few simple typos or minor bugs can generate more 

In 4DOS (not in command.com):

command >& filename    To redirect standard output and standard error to a
                       file or device
command >&> filename   To redirect standard error only to a file or device

You can get a handy scrollable/searchable list with

gcc <params> |& list/s

	-trout

--
"We are what we pretend to be, so we must be careful
 about what we pretend to be."
                                     - Kurt Vonnegut

-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".

- Raw text -