-
Bug
-
Resolution: Fixed
-
P3
-
9
-
Chinese or Japanese locale Windows (similar locales probably also impacted).
Since "warnings as errors" has been enabled in JDK 9, the presence of non-ASCII characters in source code for lcms and harfbuzz is causing Windows builds fail in a number of non-English locales. (See attached warnings_log.txt for the exact warnings.)
Obviously, we want to be able to build OOTB regardless of the user's locale. There does not appear to be a simple workaround like issuing a chcp command before building or setting environmental variables. The only way to build the code as-is on these systems is to change the system-wide "language for non-Unicode programs" (which requires a reboot!) or to disable warnings as errors during configuration (--disable-warnings-as-errors). Obviously neither is a very good solution.
Obviously, we want to be able to build OOTB regardless of the user's locale. There does not appear to be a simple workaround like issuing a chcp command before building or setting environmental variables. The only way to build the code as-is on these systems is to change the system-wide "language for non-Unicode programs" (which requires a reboot!) or to disable warnings as errors during configuration (--disable-warnings-as-errors). Obviously neither is a very good solution.