From:	Svein Ove Aas <ketilaas AT online DOT no>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: Saving gcc's messages
Date:	Fri, 31 Jul 1998 10:54:37 +0200
Organization:	Telenor Online Public Access
Lines:	28
Message-ID:	<35C1864C.D0AAFDC3@online.no>
References:	<35c476e4 DOT 79147412 AT nntp1 DOT best DOT com>
NNTP-Posting-Host:	ti33a95-0109.dialup.online.no
Mime-Version:	1.0
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp

Mike Pooler wrote:

> Hi! Since this is my first post, let me say how thrilled I am about
> the existence of djgpp! I just discovered it today, and I'm very VERY
> excited about the flat-memory model!
>
> Here's a simple question (I hope). When I run gcc from the
> command-line in a DOS shell, the compiler messages (warnings and
> errors) are printed on the screen. When I try to redirect these, as
> in:
>
> gcc -c test.c > err.txt
>
> It doesn't work- err.txt stays empty, and the errors are still printed
> on the screen.

That's because it's written to stderr, not stdout.
The > operator only redirects stdout.
There's a program in the DJGPP package that can redirect stderr for you.
I don't remember it's name, though.

P.S. Get rhide.
It's much easier to program in, and the whole problem goes away.
When you feel like it, get Allegro.

- Raw text -