Date:	Mon, 14 Nov 1994 09:35:39 -0500 (CDT)
From:	Aaron Ucko <UCKO AT VAX1 DOT ROCKHURST DOT EDU>
Subject:	Re: Diags when compiling.
To:	TAUPIN AT rsovax DOT lps DOT u-psud DOT fr
Cc:	djgpp AT sun DOT soe DOT clarkson DOT edu
Organization:	Rockhurst College; Kansas City, MO

>Subj:  Diags when compiling.
 ^^^^ It would save everyone a lot of trouble if you used normal RFC-822
headers...what mailer are you using?
>
>When gcc makes diags, they are written on the screen. But the claassical
>DOS piping (i.e. saying gcc -c myfile.c >myfile.log) does not work.
>
>In order to show my problems to others, how can I make the diags
>go to a file, not [only] to screen ?

Here we go again.  Basically, the problem is that diags appear on stderr, but
> redirects stdout.  You have several options for correcting this situation:
a) Use 4DOS or another shell which allows stderr redirection.
b) Put 2r1 in your GO32 environment variable (note: this may redirect
preprocessor diagnostics into compiler input and confuse the @#$ out of it--at
least it did in 1.11 [I got 4DOS before 1.12 :-)].  YMMV.)
OK, so that wasn't several. Sorry! :-)

--- Aaron Ucko (ucko AT vax1 DOT rockhurst DOT edu; finger for PGP public key) -=- httyp!
-=*=-Just because you're paranoid doesn't mean they aren't out to get you.-=*=-
Geek code 2.1 [finger hayden AT vax1 DOT mankato DOT msus DOT edu for explanation]: 
 GCS/M/S d(-) H s g+ p? !au a-- w+ v+ C++(+++)>++++ U-(S+)>++++ P+ L>++ 3(-) 
 E-(----) !N>++ K- W(--) M-(--) V(--) po-(--) Y+(++) t(+) !5 j R G tv--(-) 
 b+++ !D(--) B--(---) e>++++(*) u++(@) h!() f(+) r-(--)>+++ n+(-) y?

- Raw text -