Date:	Thu, 3 Mar 94 18:32:42 EST
From:	peprbv AT cfa0 DOT harvard DOT edu (Bob Babcock)
To:	cigna AT helios DOT phy DOT ohiou DOT edu
Cc:	djgpp AT sun DOT soe DOT clarkson DOT edu
Subject:	Re: redirecting stderr
Reply-To:	babcock AT cfa DOT harvard DOT edu

> I tried this [2r1 in the GO32 environment variable]. It sent stderr
> somewhere, but it wasn't stdout. No error messages appeared on the screen and
> redirecting them to a file produced an empty file.

I'll have to admit that I don't use 2r1 myself.  I use OPUS make which lets
me use 2>&1>>filename in my makefile.  One possibility: did you use > rather
than >> when redirecting to a file?  If so, you would only see errors from
the last step, and perhaps it didn't have any errors.

If 2r1 is broken, and you don't want to pay for 4dos, there are other
possibilities for redirecting stderr at oak.oakland.edu.  I once tested one
of these, I think redir.zip, with an older version of djgpp.

Directory pub/msdos/sysutil/
 Filename   Type Length   Date    Description
==============================================
rdstderr.zip  B    5394  880306  Redirect STDERR to a file, with src
redir.zip     B    7951  900803  Combines STDERR with STDOUT for redirection
redview3.zip  B    6719  920824  View redirected output on screen, w/ASM source
tee11.zip     B    2640  880921  Redirect output to std out & screen v1.1 8/88

- Raw text -