delorie.com/archives/browse.cgi | search |
From: | "Tom Leete" <tleete AT access DOT mountain DOT net> |
Newsgroups: | comp.os.msdos.djgpp |
References: | <6osijo$1b4 AT newsops DOT execpc DOT com> |
Subject: | Re: stdout - stderr question |
Date: | Sun, 19 Jul 1998 15:17:58 -0400 |
Lines: | 17 |
NNTP-Posting-Host: | 198.77.57.131 |
Message-ID: | <35b24631.0@news.mountain.net> |
To: | djgpp AT delorie DOT com |
DJ-Gateway: | from newsgroup comp.os.msdos.djgpp |
yes, use &> --TML-- Pat O'Hara wrote in message <6osijo$1b4 AT newsops DOT execpc DOT com>... >I use codewright with djgpp. It uses '>' (stdout) to capture the output >of a command and show the "errors" (i.e. gcc -o Main.exe Main.c > >projerr.txt). This does not capture the output from gcc. So being a >Unix hack I figured I'ld go out to the command line and run gcc -o >Main.exe Main.c 2> projerr.txt. This also did not capture the output. >Does anyone know how to capture the stderr output of a DOS process >running under Windows 95? > >Tanks for your suport >PatO >
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |