Hello,
Oracle still builds JDK 10 and 11 using Xcode 6.3 using the Macosx10.9
sdk. We are warning free there. Using newer versions of Xcode is known
to produce warnings.
I'm currently in the process of updating the toolchain versions and
platforms we use at Oracle so this should get fixed in the near future
for JDK 11. Note though that it will deteriorate again with even newer
versions of Xcode unless someone else provides fixes for it before we
switch toolchain versions again.
/Erik
On 2018-02-01 09:57, Alan Snyder wrote:
On Feb 1, 2018, at 9:05 AM, Erik Joelsson <erik.joels...@oracle.com
<mailto:erik.joels...@oracle.com>> wrote:
Regarding warning chasing. I agree that we it's not feasible to chase
down every warning in every version of GCC, or any other toolchain,
but I also think that for platforms/configurations where people are
actively developing changes for OpenJDK, it makes sense to try to
keep it clean. This helps prevent new code from introducing warnings.
For the configurations Oracle use, we keep a strict -Werror policy
because we want the code to be clean
Is it not the case that building on macOS requires
-disable-warnings-as-errors? Or is that only the case on more recent
macOS releases that used by Oracle?
Alan
