delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/1994/03/03/04:36:05

Subject: Re: gcc output...
To: andyh AT cimage DOT com (Andy Hore)
Date: Thu, 3 Mar 1994 09:44:26 +0100 (MET)
From: Henrik Storner <storner AT olicom DOT dk>
Cc: djgpp AT sun DOT soe DOT clarkson DOT edu

> 	Just a quick question. gcc warning and error output gets
> displayed on stderr, rather than stdout. Is there any way of sending
> this to a file and/or the screen?

Bob Babcock just posted how to do it by setting the go32 environment
variable, so I won't go into that.

Another solution to this problem is to stop using command.com, and re-
place it with another command interpreter that supports redirecting
stderr. 4DOS (and NDOS) will do this:

	> filename   - redirect stdout only
	>& filename  - redirect stdout and stderr
	>&> filename - redirect stderr only

It has the advantage - over the go32 solution - that it works with all
programs, not just those using go32.
-- 
Henrik Storner        | "The effort of using machines to mimic the human mind
(storner AT olicom DOT dk)   |  has always struck me as rather silly. I would rather
System Engineering    |  use them to mimic something better."
Olicom Denmark        |                                   Edsger Dijkstra.

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019