Problems about building JDK9 on windows

Amanda Jiang amanda.jiang at
Thu Apr 17 23:17:10 UTC 2014

Hi Volker,

As Erik mentioned, is not existed.

The toolchain detection part from config.log are pasted below:

Command: /cygdrive/c/Users/amjiang/workspace/tools/jdk1.8.0/bin/java 
-Xmx512M -version
configure:26179: result:  -XX:+UseSerialGC -Xms32M -Xmx512M
configure:26624: Using default toolchain microsoft (Microsoft Visual Studio)
configure:26657: checking for link
configure:26675: found /cygdrive/c/Program Files (x86)/Microsoft Visual 
Studio 10.0/VC/bin/link
configure:26687: result: /cygdrive/c/Program Files (x86)/Microsoft 
Visual Studio 10.0/VC/bin/link
configure:26696: checking if the first found link.exe is actually the 
Cygwin link tool
configure:26703: result: no
configure:26778: Found Visual Studio installation at /cygdrive/c/Program 
Files (x86)/Microsoft Visual Studio 10.0/ using VS100COMNTOOLS variable
configure:27348: Rewriting VS_ENV_CMD to 
configure:27354: Trying to extract Visual Studio environment variables
configure:27423: Setting extracted environment variables
configure:27435: checking for Visual Studio variables
configure:27444: result: ok
configure:27650: checking for cl
configure:27668: found /cygdrive/c/Program Files (x86)/Microsoft Visual 
Studio 10.0/VC/BIN/cl
configure:27680: result: /cygdrive/c/Program Files (x86)/Microsoft 
Visual Studio 10.0/VC/BIN/cl
configure:27991: Rewriting CC to "/cygdrive/c/progra~2/micros~2.0/vc/bin/cl"
configure:28000: checking resolved symbolic links for CC
configure:28050: result: /cygdrive/c/progra~2/micros~2.0/vc/bin/cl
configure:28053: checking if CC is disguised ccache
configure:28491: result: no, keeping CC
configure:28612: Using microsoft C compiler version 16.00.30319.01 
[Microsoft (R) 32-bit C/C++ Optimizing Compiler Version 16.00.30319.01 
for 80x86]
configure:28729: checking for C compiler version
configure:28738: /cygdrive/c/progra~2/micros~2.0/vc/bin/cl --version >&5
Microsoft (R) 32-bit C/C++ Optimizing Compiler Version 16.00.30319.01 
for 80x86
Copyright (C) Microsoft Corporation.  All rights reserved.


On 4/17/14 1:37 AM, Erik Joelsson wrote:
> Hello Volker,
> On 2014-04-17 10:26, Volker Simonis wrote:
>> Hi,
>> what is ""? I can not find that in my output directory.
>> I think the variables INCLUDE and LIB from which VS_INCLUDE and VS_LIB
>> are derived are in <output-dir>/
> That depends what source you are building. Magnus recently changed the 
> part of configure that extracts these variables from Visual Studio.
>> Amanda, could you please also post the contents of 
>> <output-dir>/
> Since you have, will not be found.
>> Also please post the part of config.log where the toolchain detection
>> starts (i.e. something like "configure:26374: Using default toolchain
>> microsoft (Microsoft Visual Studio)") up tot he part you already
>> posted.
> Yes, this would be the next place to look.
> /Erik
>> Regards,
>> Volker
>> On Thu, Apr 17, 2014 at 1:02 AM, Magnus Ihse Bursie
>> <magnus.ihse.bursie at> wrote:
>>> On 16 apr 2014, at 21:00, Amanda Jiang <amanda.jiang at> wrote:
>>>> VS_INCLUDE=" "
>>>> VS_LIB=" "
>>> These should not be empty. It is the cause of your failures. The 
>>> question is why they are empty, though...
>>> /Magnus

More information about the build-dev mailing list