delorie.com/archives/browse.cgi | search |
From: | "Pat O'Hara" <pdohara AT execpc DOT com> |
Newsgroups: | comp.os.msdos.djgpp |
Subject: | stdout - stderr question |
Date: | Sun, 19 Jul 1998 05:48:47 -0500 |
Organization: | Exec-PC BBS Internet - Milwaukee, WI |
Lines: | 11 |
Message-ID: | <6osijo$1b4@newsops.execpc.com> |
NNTP-Posting-Host: | dantooine-2-33.mdm.mke.execpc.com |
Mime-Version: | 1.0 |
To: | djgpp AT delorie DOT com |
DJ-Gateway: | from newsgroup comp.os.msdos.djgpp |
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 |