Path: chuka.playstation.co.uk!news
From: Ken Lam <100411.265@compuserve.com>
Newsgroups: scee.yaroze.programming.gnu_compiler
Subject: Re: Redirect gcc >file
Date: Wed, 23 Apr 1997 11:11:50 -0700
Organization: PlayStation Net Yaroze (SCEE)
Lines: 52
Message-ID: <335E50E6.221@compuserve.com>
References: <335BF646.AD6@compuserve.com> <335AF994.28F6@micronetics.com>
NNTP-Posting-Host: ld53-095.lon.compuserve.com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Mailer: Mozilla 2.02 (Win16; I)

>>
> I'd like to collect all the error messages so that I can view them at

        Thats because errors get written to stderr.

        Try gcc >& gcc.err

        Hope that helps

        Jim
<<
Thanks for the tip but it doesn't seem to work: if I use

  gcc loadsave.c >& gcc.err

I get 
  gcc.exe: gcc.err: file not found

and a file of zero size called `&' gets created.

Looks like I might have to go back to Codewarrior -- does anyone actually 
*like* it or use the thing?

Ken Lam
ESP Software

PS Non-Yaroze question:
And why can't I seem to use redirection in Windows 95 at all? Something 
like
   dir /s /b | grep -ir .*10\.c
makes the dir command throw the error too many arguments or a file `grep' 
gets created.Jim wrote:
> 
> Ken Lam wrote:
> >
> > I have tried redirecting gcc's output to a file
> >   gcc xxx.c > file.txt
> > but all the text still goes to the screen.
> >
> > I'd like to collect all the error messages so that I can view them at
> > leisure later : (
> >
> > Ken Lam
> > ESP Software
> 
>         Thats because errors get written to stderr.
> 
>         Try gcc >& gcc.err
> 
>         Hope that helps
> 
>         Jim