Date:	Thu, 30 Jun 94 19:49:02 EDT
From:	peprbv AT cfa0 DOT harvard DOT edu (Bob Babcock)
To:	philip AT irl DOT chch DOT cri DOT nz
Cc:	djgpp AT sun DOT soe DOT clarkson DOT edu
Subject:	Re: RFC: Problems with GO32=2r1 and GCC error messages.
Reply-To:	babcock AT cfa DOT harvard DOT edu

> When using GO32=2r1 to redirect stderr so that I can pipe the error messages
> from gcc into a file, Errors that occurr during the CPP phase do not get
> written so the screen (or redirected file)
> ...
> Can someone confirm if this is a generic problem or just something with
> my particular PC setup.

This has come up before.  I think the problem was that cpp output is on
stdout, and gets redirected or piped to cc1.  When you redirect stderr to
stdout, the cpp errors also get sent to cc1.  I don't recall any good
solution (other than not making errors that the preprocessor can catch).

- Raw text -