Xref:	news2.mv.net comp.os.msdos.djgpp:3794
From:	mcantos AT ocean DOT com DOT au (Marcelo Cantos)
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: gcc messages > file
Date:	Sun, 12 May 96 11:37:02 GMT
Organization:	(private)
Lines:	16
Distribution:	world
Message-ID:	<4n4m1d$cdo@news.mel.aone.net.au>
References:	<Pine DOT VUL DOT 3 DOT 91 DOT 960415123808 DOT 14476F-100000 AT zeus DOT adv-boeblingen DOT de> <317258AF DOT 61C1 AT Mathematik DOT tu-chemnitz DOT de> <4lclse$d2c AT yama DOT mcc DOT ac DOT uk> <4livp3$892 AT trog DOT dra DOT hmg DOT gb>
NNTP-Posting-Host:	203.12.234.184
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp

In article <4livp3$892 AT trog DOT dra DOT hmg DOT gb>, itmiller AT taz DOT dra DOT hmg DOT gb (Ian Miller) wrote:
>
>In article <4lclse$d2c AT yama DOT mcc DOT ac DOT uk>, tpj AT sn2 DOT ee DOT umist DOT ac DOT uk (TPJ Mc Guigan)
> writes:
>|>
>|>Hmmm, what about redirecting stderr via "gcc file.c >& err.msg"? Don't know
>|>if this type of arrangement is what you want. Just in case it is ---
>|>
>|>  >   redirects stdout
>|>  >&  redirects stderr and stdout
>|>  >&> redirects stderr
>
>In DOS?

As far as I know these redirection options are not available in DOS. I am able 
to use them with 4DOS, a command shell from jpsoft (http://www.jpsoft.com).

- Raw text -