www.delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/1996/07/04/05:15:17

Xref: news2.mv.net comp.os.msdos.djgpp:5641
From: dthomson AT gssec DOT bt DOT co DOT uk (David Thomson)
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Screen capture of compilations
Date: 4 Jul 1996 07:56:28 GMT
Organization: BT Glasgow Engineering Centre
Lines: 35
Sender: dthomson AT ocelot (David Thomson)
Distribution: world
Message-ID: <4rftfc$n94@cheetah.gssec.bt.co.uk>
References: <3045147437 DOT 0 DOT p00088 AT psilink DOT com>
NNTP-Posting-Host: ocelot.gssec.bt.co.uk
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp

In article <3045147437 DOT 0 DOT p00088 AT psilink DOT com>, "paul winner" <p00088 AT psilink DOT com> writes:
|> I'm trying to capture the output of my V2 compilations so that I can 
|> cleanup the -Wall errors.  With BC and MSC you could run things like:
|> 
|> make foo > warnings.foo
|> 
|> and get a file showing everything that had displayed to the screen.
|> 
|> With djgpp make foo > warnings.foo gives a warnings.foo file which 
|> contains the steps as progressed through the makefile, ie:
|> 
|> gcc -c -O -I../include tile.o tile.c
|> 
|> and warnings to the screen (ie, '/* used in comment'), but the piped 
|> file and the screen don't match at all.
|> 
|> PS: Is there an explanation somewhere for the command line /W options?

Hi

gcc sends warnings & error messages to stderr, not stdout, which is what
DOS pipes to the file.  To do what you want, you need to use the `redir'
program (should be in your \bin directory), with something like:
  redir -e make warnings.foo

I'd double check the command ordering, since I may have that the wrong
way round.

Cheers

Dave

-------
the games kitchen : http://www.not.available.com
                  : e-mail: Thomson AT btinternet DOT com

- Raw text -


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