Any plans to add support for -Wno-incompatible-pointer-types?

331 views
Skip to first unread message

vitaly.kru...@gmail.com

unread,
Apr 16, 2016, 5:28:30 PM4/16/16
to mingwpy
Using anaconda-based mingwpy on Win64: cc1.exe: warning: unrecognized command line option "-Wno-incompatible-pointer-types". gcc version 4.9.2

The option `-Wno-incompatible-pointer-types` is very useful for suppressing unnecessary warnings when building 3rd-party sources. The gcc-4.8 compiler (as well as clang) that I use for building my projects on linux appears to support this option, but mingwpy toolchain complains.

Is this the appropriate forum for it, or should I repost on mingw-64?

Many thanks.




carlkl

unread,
Apr 16, 2016, 5:36:39 PM4/16/16
to mingwpy, vitaly.kru...@gmail.com
This is strange,

running mingwpy gcc or g++ on an emtpy file with this flags works flawless, at least on my machine.

Cheers,

Carl

vitaly.kru...@gmail.com

unread,
Apr 16, 2016, 5:59:09 PM4/16/16
to mingwpy, vitaly.kru...@gmail.com
Hi Carl,

I made a similar observation to yours concerning -Wno-incompatible-pointer-types: If a source file didn't contain code that triggered warnings, then `cc1.exe: warning: unrecognized command line option "-Wno-incompatible-pointer-types"` wasn't printed by the toolchain.

Here is a more complete example of the occurrence of this warning:

C:\Users\Administrator\nta\nupic.core\build\scripts\ThirdParty\Source\Apr1StaticLib\misc\win32\apr_app.c:79:29: warning:
 passing argument 3 of 'main' from incompatible pointer type
     return main(argc, argv, env);
                             ^
C:\Users\Administrator\nta\nupic.core\build\scripts\ThirdParty\Source\Apr1StaticLib\misc\win32\apr_app.c:48:12: note: ex
pected 'const char **' but argument is of type 'char **'
 extern int main(int argc, const char **argv, const char **env);
            ^
C:\Users\Administrator\nta\nupic.core\build\scripts\ThirdParty\Source\Apr1StaticLib\misc\win32\apr_app.c: At top level:
Reply all
Reply to author
Forward
0 new messages