delorie.com/archives/browse.cgi | search |
Date: | Wed, 25 Apr 2001 18:51:19 +0300 |
From: | "Eli Zaretskii" <eliz AT is DOT elta DOT co DOT il> |
Sender: | halo1 AT zahav DOT net DOT il |
To: | djgpp AT delorie DOT com |
Message-Id: | <7263-Wed25Apr2001185119+0300-eliz@is.elta.co.il> |
X-Mailer: | Emacs 20.6 (via feedmail 8.3.emacs20_6 I) and Blat ver 1.8.9 |
In-reply-to: | <3ae6dc8f.13867961@news.earthlink.net> (dan@no.spam) |
Subject: | Re: Seeing errors from gcc in DOS |
References: | <3ae6dc8f DOT 13867961 AT news DOT earthlink DOT net> |
Reply-To: | djgpp AT delorie DOT com |
Errors-To: | nobody AT delorie DOT com |
X-Mailing-List: | djgpp AT delorie DOT com |
X-Unsubscribes-To: | listserv AT delorie DOT com |
> From: dan AT no DOT spam > Newsgroups: comp.os.msdos.djgpp > Date: Wed, 25 Apr 2001 14:17:28 GMT > > There's a syntax error in my program that's generating a ton of errors. The > problem is, the first error - the cause of all the calamity - scrolls right out > of the window. > > I've tried piping the output to more ( gcc -c -Wall cname.c | more ). No luck. > Keeps flying by. > > I've tried redirecting output to a file. ( gcc -c -Wall cname.c > e.txt ). It > creates e.txt, but it's blank. > > I've tried redirecting stderr ( 3>e.txt ). Ditto. Use the program `redir' supplied with DJGPP. The details are in section 6.15 of the DJGPP FAQ list, which also describes a few more ways to catch the error messages from the compiler.
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |