| delorie.com/archives/browse.cgi | search |
| From: | Roberto Henriquez Laurent <shl24634 AT alumnos DOT inf-cr DOT uclm DOT es> |
| Newsgroups: | comp.os.msdos.djgpp |
| Subject: | Re: newbie question |
| Date: | Thu, 05 Jun 1997 10:14:32 +0200 |
| Organization: | Universidad de Castilla-La Mancha |
| Lines: | 24 |
| Message-ID: | <33967568.86D22F4A@alumnos.inf-cr.uclm.es> |
| References: | <5n55td$6s1$1 AT morgoth DOT sfu DOT ca> |
| NNTP-Posting-Host: | est271.mag-cr.uclm.es |
| Mime-Version: | 1.0 |
| To: | djgpp AT delorie DOT com |
| DJ-Gateway: | from newsgroup comp.os.msdos.djgpp |
Wilson Wang Shun Leung wrote:
> This is a newbie question. Sorry if it is too trivial.
> How to capture error/warning message from command line
> (in DOS)? I tried :
> gcc -c prog.c | more
>
> But the piping doesn't work.
>
> or
> gcc -c prog.c > err
You need to redirect *standard error* instead of standard output. I
don't know if COMMAND.COM is able to do that. I use 4DOS & NDOS, which
can. (However I don't remember the exact syntax now...)
> But the err file is empty
>
> Any idea?
>
> Thanks
| webmaster | delorie software privacy |
| Copyright © 2019 by DJ Delorie | Updated Jul 2019 |