Date:	Wed, 24 Aug 1994 18:46:38 -0500 (CDT)
From:	"Troy D. VanHorn" <tvanhorn AT ozarks DOT sgcl DOT lib DOT mo DOT us>
Subject:	capturing GCC error msgs.
To:	djgpp AT sun DOT soe DOT clarkson DOT edu

How does one capture the error messages GCC spits out if it encounters 
errors?  I've had programs with only 1 to 2 errors cause several 
screenfulls of error messages, and because they scroll off the screen so 
fast, I don't have a chance to see the first ones which are the most 
important ones.  I've tried redirecting or piping, but that doesn't 
work.  The only thing that has worked so far is to hit the turbo button 
to slow things down, and then recompile and press CTRL-S when the 
messages start to appear.  There u^

- Raw text -