Date:	Thu, 25 Aug 94 11:40:58 EDT
From:	peprbv AT cfa0 DOT harvard DOT edu (Bob Babcock)
To:	mwijz AT phys DOT uva DOT nl
Cc:	djgpp AT sun DOT soe DOT clarkson DOT edu
Subject:	Re: Logfile
Reply-To:	babcock AT cfa DOT harvard DOT edu

> Is there a way to get the error messages of the DJGPP compiler
> into a log file? `gcc xxx.c > xxx.log' does not work. I would
> like to see the errors while editing the source.

The error messages come out on stderr.  To get them into a file, you can
1. SET GO32=2r1 redirects stderr to stdout for all go32 programs.
2. Use 4DOS which supports stderr redirection.
3. Use a make which supports stderr redirection.  OPUS make (commercial)
   which I use does this. 
4. Use a DOS utility which redirects stderr.  Some examples at oak.oakland.edu
   include
Directory SimTel/msdos/c/
 Filename   Type Length   Date    Description
==============================================
redirect.c    A    2699  890427  Feed line to shell w/stdin/stdout/stderr redir
Directory SimTel/msdos/sysutil/
 Filename   Type Length   Date    Description
==============================================
rdstderr.zip  B    5394  880306  Redirect STDERR to a file, with src
redir.zip     B    7951  900803  Combines STDERR with STDOUT for redirection

(I have successfully tested the last of these.)  It has been claimed, but I
have not verified, that redirecting stderr may cause preprocessor error
messages to be fed to cc1 rather than being displayed.

- Raw text -