--- old/doc/building.html 2020-07-06 21:02:09.340373106 -0400 +++ new/doc/building.html 2020-07-06 21:02:08.896358193 -0400 @@ -283,7 +283,7 @@

The JDK is currently known to be able to compile with at least version 9.2 of gcc.

In general, any version between these two should be usable.

clang

-

The minimum accepted version of clang is 3.2. Older versions will not be accepted by configure.

+

The minimum accepted version of clang is 3.5. Older versions will not be accepted by configure.

To use clang instead of gcc on Linux, use --with-toolchain-type=clang.

Apple Xcode

The oldest supported version of Xcode is 8.

@@ -292,9 +292,8 @@

It is advisable to keep an older version of Xcode for building the JDK when updating Xcode. This blog page has good suggestions on managing multiple Xcode versions. To use a specific version of Xcode, use xcode-select -s before running configure, or use --with-toolchain-path to point to the version of Xcode to use, e.g. configure --with-toolchain-path=/Applications/Xcode8.app/Contents/Developer/usr/bin

If you have recently (inadvertently) updated your OS and/or Xcode version, and the JDK can no longer be built, please see the section on Problems with the Build Environment, and Getting Help to find out if there are any recent, non-merged patches available for this update.

Microsoft Visual Studio

-

The minimum accepted version of Visual Studio is 2010. Older versions will not be accepted by configure. The maximum accepted version of Visual Studio is 2019. Versions older than 2017 are unlikely to continue working for long.

-

If you have multiple versions of Visual Studio installed, configure will by default pick the latest. You can request a specific version to be used by setting --with-toolchain-version, e.g. --with-toolchain-version=2015.

-

If you get LINK: fatal error LNK1123: failure during conversion to COFF: file invalid when building using Visual Studio 2010, you have encountered KB2757355, a bug triggered by a specific installation order. However, the solution suggested by the KB article does not always resolve the problem. See this stackoverflow discussion for other suggestions.

+

The minimum accepted version of Visual Studio is 2017. Older versions will not be accepted by configure and will not work. The maximum accepted version of Visual Studio is 2019.

+

If you have multiple versions of Visual Studio installed, configure will by default pick the latest. You can request a specific version to be used by setting --with-toolchain-version, e.g. --with-toolchain-version=2017.

IBM XL C/C++

Please consult the AIX section of the Supported Build Platforms OpenJDK Build Wiki page for details about which versions of XLC are supported.

Boot JDK Requirements

--- old/doc/building.md 2020-07-06 21:02:10.540413414 -0400 +++ new/doc/building.md 2020-07-06 21:02:10.100398635 -0400 @@ -323,7 +323,7 @@ ### clang -The minimum accepted version of clang is 3.2. Older versions will not be +The minimum accepted version of clang is 3.5. Older versions will not be accepted by `configure`. To use clang instead of gcc on Linux, use `--with-toolchain-type=clang`. @@ -355,20 +355,13 @@ ### Microsoft Visual Studio -The minimum accepted version of Visual Studio is 2010. Older versions will not -be accepted by `configure`. The maximum accepted version of Visual Studio is -2019. Versions older than 2017 are unlikely to continue working for long. +The minimum accepted version of Visual Studio is 2017. Older versions will not +be accepted by `configure` and will not work. The maximum accepted +version of Visual Studio is 2019. If you have multiple versions of Visual Studio installed, `configure` will by default pick the latest. You can request a specific version to be used by -setting `--with-toolchain-version`, e.g. `--with-toolchain-version=2015`. - -If you get `LINK: fatal error LNK1123: failure during conversion to COFF: file -invalid` when building using Visual Studio 2010, you have encountered -[KB2757355](http://support.microsoft.com/kb/2757355), a bug triggered by a -specific installation order. However, the solution suggested by the KB article -does not always resolve the problem. See [this stackoverflow discussion]( -https://stackoverflow.com/questions/10888391) for other suggestions. +setting `--with-toolchain-version`, e.g. `--with-toolchain-version=2017`. ### IBM XL C/C++