[Numpy-discussion] numpy.distutils does not output compilation warning on win32 ?
Mon Jan 21 06:13:00 CST 2008
If I remember correctly then the warnings were disabled because
when compiling numpy/scipy on windows there were *lots* of
warnings, especially for pyrex generated sources.
When there is an error, all warnings will be shown. Hmm, and on
linux the warnings should also be shown (this actually depends on what
Python distutils one is using as the distutils logging interface
has been changed between Python versions). In any case, we can enable
all the warnigs again with no problems (may be only windows guys will
not be so happy about it).
On Mon, January 21, 2008 8:44 am, David Cournapeau wrote:
> I noticed a strange behaviour with distutils: when compiling C code
> on windows (using mingw), the compilation warning are not output on the
> console. For example, umathmodule.c compilation emits the following
> numpy\core\src\umathmodule.c.src:128: warning: static declaration of
> 'acoshf' follows non-static declaration
> numpy\core\src\umathmodule.c.src:136: warning: static declaration of
> 'asinhf' follows non-static declaration
> I think this is coming from distutils because when I execute the exact
> same command on the shell, I get those warnings. If there is an error
> (by inserting #error), then all the warnings appear also when using
> distutils, which would suggest that distutils checks the return status
> of gcc to decide when to output should be sent on the shell ? Anyway, if
> we can do something about it, I think it would be better to always
> output warnings (it took me quite a while to understand why I got
> warnings with scons and not with distutils...).
> Numpy-discussion mailing list
More information about the Numpy-discussion