Recent check-ins in Hotspot is causing linkage errors when building with VS 2013 / VS 2015.

This provokes attempts to upgrade to VS 2017 Enterprise, but it seems configure does not properly recognize this compiler environment:

checking for jarsigner in Boot JDK... ok
checking if Boot JDK is 32 or 64 bits... 64
checking for local Boot JDK Class Data Sharing (CDS)... no, creation failed
checking for Build JDK... yes, will use output dir
configure: Using default toolchain microsoft (Microsoft Visual Studio)
checking for link... /cygdrive/d/Program Files (x86)/Microsoft Visual Studio/2017/Enterprise/VC/Tools/MSVC/14.12.25827/bin/HostX86/x86/link
checking if the first found link.exe is actually the Cygwin link tool... no
configure: Found Visual Studio installation at /cygdrive/d/Program Files (x86)/Microsoft Visual Studio/2017/Enterprise/ using VS150COMNTOOLS variable
configure: Found Microsoft Visual Studio 2017
configure: Rewriting VS_ENV_CMD to "/cygdrive/d/progra~2/micros~4/2017/enterp~1/vc/auxili~1/build/vcvars~2.bat"
configure: Trying to extract Visual Studio environment variables
**********************************************************************
** Visual Studio 2017 Developer Command Prompt v15.5.1
** Copyright (c) 2017 Microsoft Corporation
**********************************************************************
[vcvarsall.bat] Environment initialized for: 'x86_x64'
configure: Could not succesfully extract the envionment variables needed for the VS setup.
configure: error: Cannot continue
configure: Try setting --with-tools-dir to the VC/bin directory within the VS installation
configure: or run "bash.exe -l" from a VS command prompt and then run configure from there.
configure exiting with result code 1