www.delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/1998/08/02/03:15:45

From: pooler AT pcgame DOT com (Mike Pooler)
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Saving gcc's messages
Date: Fri, 31 Jul 1998 14:21:15 GMT
Organization: PC Game Finder
Lines: 37
Message-ID: <35c5d274.100457988@nntp1.best.com>
References: <35c476e4 DOT 79147412 AT nntp1 DOT best DOT com> <10512 DOT 980731 AT bspu DOT unibel DOT by>
Reply-To: pooler AT pcgame DOT com
NNTP-Posting-Host: pooler.vip.best.com
Mime-Version: 1.0
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp

Alexander,

Super!! Thanks...

Mike

Alexander Bokovoy <bokovoy AT bspu DOT unibel DOT by> wrote:

>Hi Mike,
>31.07.98, you wrote:
>> 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.
>> I checked the gcc options, and didn't see any way of directing the
>> messages into a file.
>> Please let me know if I can do this- or if not, if I can do it instead
>> with the "make" utility (which I haven't tried yet)...
>DJGPP distribution has a special command redir (in
>djgpp/bin/redir.exe) which is suitable
>for such work:
>redir.exe -e error.txt -o output.txt <program-to-execute [options]>
>    -e error.txt - save content of stderr to error.txt
>    -o output.txt - save content of stdout to output.txt
>In your case it will be:
>redir.exe -e err.txt gcc -c test.c
>
>Regards,
>Alexander Bokovoy, <bokovoy AT bspu DOT unibel DOT by>
>--=== The Soft Age coming soon ===--
>
>
>

- Raw text -


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