-
Bug
-
Resolution: Fixed
-
P3
-
6
-
b32
-
generic
-
generic
Some makefiles have used COMPILER_WARNING_LEVEL=0 in favor of COMPILER_WARNINGS_FATAL=false
which means we never even see the warning errors.
This was done because on Windows the default was to treat all warnings as fatal.
This changed and we should see the warnings all the time now.
If a Makefile wants to make sure it always builds regardless of warnings then it should
use COMPILER_WARNINGS_FATAL=false.
Also see 6207938
###@###.### 2005-04-10 20:48:03 GMT
which means we never even see the warning errors.
This was done because on Windows the default was to treat all warnings as fatal.
This changed and we should see the warnings all the time now.
If a Makefile wants to make sure it always builds regardless of warnings then it should
use COMPILER_WARNINGS_FATAL=false.
Also see 6207938
###@###.### 2005-04-10 20:48:03 GMT
- relates to
-
JDK-6396601 (process) ProcessImpl_md.c Windows C compiler warning purity
-
- Resolved
-
-
JDK-6207938 Need some way to track the compiler warning messages from the RE builds (all platforms)
-
- Closed
-