From: jqb AT netcom DOT com (Jim Balter)
Subject: Re: Catching g++ error output
18 Apr 1997 06:24:26 -0700
Approved: cygnus DOT gnu-win32 AT cygnus DOT com
Distribution: cygnus
Message-ID: <33576D30.3509.cygnus.gnu-win32@netcom.com>
References: <Pine DOT A32 DOT 3 DOT 91 DOT 970418010547 DOT 20142E-100000 AT pegasus DOT unm DOT edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Mailer: Mozilla 3.01Gold (WinNT; I)
Original-To: James Paul Morgan <jpmorgan AT unm DOT edu>
Original-CC: gnu-win32 AT cygnus DOT com
Original-Sender: owner-gnu-win32 AT cygnus DOT com

James Paul Morgan wrote:
> 
> Well, this question is less about the Cygnus win32 itself and more about
> one of the tools included with it, but...
> 
> 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
> than a screen-full of output, and so I loose the earliest lines.
> 
> On UNIX w/ Xwindows, I can just scroll back within the window.  But
> Windows95 doesn't have that option.  I've tried using '>' to dump it into
> a file, but that didn't work.  (I didn't expect it to as it doesn't on
> UNIX, but I figured I'd try.)
> 
> Any suggestions of some way to manipulate the bash or possibly an add-on
> I could download or some simple trick I've just missed would be appreciated.
> 
> See ya around the Mulberry bush.

You might read up on stderr, bash, redirection of the former by the
latter, and so on.  Any unix textbook or newsgroup will do.

--
<J Q B>
-
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".