Mail Archives: djgpp/1996/04/14/19:47:44
Tom Sgouros (tomss AT ids DOT net) writes:
> Can anyone tell me how to record the voluminous error messages that the
> code I am working on generates? (I am porting a big program that was
> compiled under WATCOM, and am seeing oceans of undefined references.) The
> DOS redirection seems only to redirect standard output, and I guess these
> are all written onto the error output, and are not redirected. I can't
> figure out how to redirect the DOS error output, and I can't find a
> 'logfile' option to djgpp, either.
You can redirect stderr to a file with an obscure go32 option listed in
the FAQ somewhere, but it has a side effect: once in a while the error
messages thus redirected end up in the .a files and other files generated
along the compile, assemble, link chain! These of course completely mess
up compilation. Obviously, for its inner workings cc1 or some such
redirects stderr while compiling temporary .a files, which seems
rather stupid to me...they must have their reasons, obscure though these
are.
As a result this redirection is not that great, and I know of no
alternative that works perfectly. This is one of the compiler's
downsides... maybe V2 has a fix for this.
--
.*. "Clouds are not spheres, mountains are not cones, coastlines are not
-() < circles, and bark is not smooth, nor does lightning travel in a
`*' straight line." ,------------------------------------------------
-- B. Mandelbrot | Paul Derbyshire (PGD) ao950 AT freenet DOT carleton DOT ca
- Raw text -