Mail Archives: djgpp/1992/10/12/10:41:39
>Re error redirection. If the preprocessor produces an error, say
>because it cannot find an include file due to a typo, I find that it
>quits with no visible error message; compiling with -E oes not help,
>though if I compile with E and redirect output to a file, as with
>gcc -E prog.cc > temp
>then the file "temp" DOES have usefule error messages in it. This is
>the kind of thing which confuses novices! Incidentally, I have 1r2 in
>the environment variable. Is there a way of getting preprocessor
>errors straight to the screen as with compiler messages?
Could this issue be related to the general problem that lots of GO32
error msgs goto to stdou instead of stderr? I reported this some time ago.
E.g., if you do:
go32 a.out myprog myargs > outfile
and go32 cannot open its paging file (e.g., you are running on a network
and do not have write rights to the root), what you get is a 47 byte outfile.
- Raw text -