From: afn03257 AT freenet3 DOT afn DOT org (Daniel P Hudson)
Newsgroups: comp.os.msdos.djgpp
Subject: Re: About redirection...
Date: 22 Jan 1997 01:32:41 GMT
Lines: 26
Message-ID: <5c3qnp$qmi@huron.eel.ufl.edu>
References: <Pine DOT LNX DOT 3 DOT 93 DOT 970121093239 DOT 6000K-100000 AT cinf DOT usm DOT md>
NNTP-Posting-Host: freenet3.afn.org
NNTP-Posting-User: afn03257
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp

Adrian Oboroc <ash AT cinf DOT usm DOT md> wrote:
>"John M. Aldrich" <fighteer AT cs DOT com> wrote:
>>Gautam N. Lad wrote:

>>> QUESTION:
>>> How do I direct the errors/warnings that are created after compile,
>>> to a file?  I tried REDIR, but didn't have a clue on how to use it.
>>> Since my HD space is limited, I got rid of the DOCs.

>>redir -o err -eo gxx -o tb.exe tb.cpp window.cpp -lgrx20

>>This redirects both stdout and stderr to the file called "err".  redir
>>has a bunch of similar options; just type "redir" to see them.

>Sorry men, but I think using redir isn't too comfortable (but it's a
>working solution, of couse), and using DOS-port of BASH is easy only
>for persons with previous experiense in UNIX ( not my case :~(  )
>Probably the best solution is to rewrite startup code in such a way,
>that it will:

I think rewritting you own simple command interpreter OR
getting something like 4DOS is the easiest solution.

Other than that, with a little dos knowledge and debug you could write
a program to point stderr to whatever stdout is and add it to an
autoexec.bat/config.sys.