Re: compilation with windows compilers

Thank you for you answer Stephen!

Well on your suggestion I tried redirecting the error, at both the whole
compilation command (M-x compile; command) and the related lines in the
makefile. But it didn't work.

Actually I discovered that the shell in Xemacs (M-x shell) has this
problem too!! That is the STDERR messages of the Compiler are
not displayed. But then again, this is *not* the case with other
win32-console programs (at least the ones I write and compile with
windows compilers). ERRs to ERRs and OUTs to OUTs :)

At first, I believed that the Compiler wrote to STDERR, since the error
redirection is working fine at the CYGWIN bash-shell. Now,  I think you
may be right that the Compiler is actually writing somewhere else and
Xemacs is not handling them properly unlike Cygwin (which is trained to
cope with windoze anomalies :)

Please accept my apologies if this will be an out of scope question, but
  how can I find out where the compiler is outputting? What else there
is to it other than STDOUT and STDERR?

Thank you,
-Levent.




Stephen J. Turnbull wrote:
>>>>>>"Levent" == Levent Yilmaz <[email protected]> writes:
> 
> 
>     Levent> I realized that somehow the output to STDOUT from the
>     Levent> compiler appears in the compilation-buffer, but the output
>     Levent> to STDERR does not.
> 
> As far as I can tell, M-x compile should mix those streams in the
> buffer.  Are you sure that the compiler isn't writing directly to the
> TTY instead of to stderr?
> 
>     Levent> I presume that the problem is due to the way Xemacs
>     Levent> redirects output. Do you have any oppinions and
>     Levent> suggestions on resolving this matter?
> 
> If you are using Cygwin, make sure the shell is bash or maybe sh, and
> you can try redirecting 2>&1 in the action part of the make rule.
> 
>